Avalara AvaTax

Calculate jurisdiction-accurate sales and use tax with Avalara AvaTax. Agents compute tax on multi-line transactions, validate and normalize customer addresses, and look up companies and tax codes before invoices go out.

5 actions Basic auth available

Avalara AvaTax website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new order lands from the storefront with a shipping address and line items

Resolve Address normalizes the ship-to address to its USPS-standardized form

The agent matches each line item to its Avalara tax code from the product mapping

Create Transaction runs as a SalesOrder document type, returning the tax quote per jurisdiction

The quoted tax attaches to the order and the invoice draft is assembled

Before the transaction is recorded as a SalesInvoice and committed, an exception review catches orders with unresolved addresses or unmapped products

Create Transaction records the invoice, and the totals post to the accounting ledger

What This Integration Enables

Sales tax is a compliance obligation wearing the costume of an arithmetic problem, and the costume fools teams into automating the wrong part first. The arithmetic is the easy part; the hard part is that the answer depends on normalized addresses, correct product classification, and jurisdiction rules that change without telling you. This connector lets FlowRunner agents run that whole pre-invoice discipline automatically, so the number on the invoice is the number the return will defend. - Compute jurisdiction-accurate sales and use tax on multi-line transactions, with ship-from and ship-to per line - Validate and normalize US and Canadian addresses before tax is calculated or a record is stored - Quote tax on orders without recording anything, then record the invoice when the sale is real - Map products to Avalara tax codes so taxability is a data decision, not a guess repeated at every sale The document-type distinction is the connector's most useful design property. An Order type returns the math and saves nothing, so agents can price tax at cart time, in quotes, and in what-if checks as often as they like. An Invoice type records the transaction, and the Commit toggle finalizes it. That separation lets a workflow calculate aggressively and file conservatively. The line between a quote and a filed record is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits: agents quote freely and commit deliberately.

Without FlowRunner

Tax by lookup table A rate table someone updates quarterly stands in for 13,000 jurisdictions changing on their own schedules

Bad addresses, bad tax A misspelled city or missing ZIP+4 silently lands the sale in the wrong jurisdiction

Exceptions found at filing The unmapped product taxed at the default rate surfaces months later, in the return

With FlowRunner

Jurisdiction-accurate tax per line Every line item calculates against its actual ship-from and ship-to, with a per-jurisdiction breakdown

Addresses cleaned before they count Resolve Address standardizes every ship-to before the tax math runs

Exceptions caught before commit Orders with resolution failures or missing tax codes pause for a person instead of filing wrong

Use Case Scenarios

Checkout tax that survives the audit

A [Shopify](/integrations/shopify) order fires the flow. The agent runs Resolve Address on the shipping address, builds the line items with their mapped tax codes, and calls Create Transaction as a SalesOrder to quote the tax. The quote and its per-jurisdiction breakdown log to [Google Sheets](/integrations/google-sheets). When the order ships, the agent re-runs Create Transaction as a SalesInvoice to record it, then books the invoice in [QuickBooks Online](/integrations/quickbooks) with the AvaTax total, not a guessed one.

The product catalog gets a taxability pass

Finance suspects half the catalog is riding the default tax code. The agent pulls the product list from [Google Sheets](/integrations/google-sheets), searches List Tax Codes for candidate classifications per product category, and writes the proposed mappings back to the sheet with the tax code description beside each. The controller reviews the proposals, corrects the edge cases, and approves. From then on, every Create Transaction call carries a deliberate tax code per line, and the mapping sheet doubles as documentation the next auditor can read without an interpreter.

Address hygiene as a nightly sweep

Customer records accumulate typos. On a schedule, the agent pulls recently added addresses from the CRM, runs each through Resolve Address, and writes back the standardized form where resolution quality is high. The addresses that fail to resolve go to a [Slack](/integrations/slack) queue for a person, because a customer whose address cannot be validated is a customer whose tax cannot be trusted, and fixing the address once beats re-litigating the jurisdiction every quarter. Ping runs at the top of every batch so credential failures surface as an alert, not as a night of silent no-ops.

Human-in-Loop Highlight

Create Transaction has two very different modes, and the difference is the whole compliance story. As a SalesOrder it returns a quote and saves nothing. As a SalesInvoice with Commit, it records a finalized transaction in AvaTax, a document that flows into tax liability and, eventually, a filed return. Committing a transaction built on an unresolved address or an unmapped product does not fail; it files confidently wrong. So FlowRunner agents commit on a leash: any transaction where Resolve Address came back with low resolution quality, or where a line fell through to the default tax code, is held uncommitted and posted to the controller with the specific doubt named. The clean majority commits straight through. The doubtful few wait for a person, because correcting a committed tax document costs far more than reviewing a flagged one.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Tax Calculation

Create Transaction Calculates sales or use tax for a multi-line transaction, with document type, company code, customer code, date, and per-line amounts, tax codes, and ship-from and ship-to addresses. Returns total tax, taxable amount, and a per-jurisdiction breakdown. Order types quote without saving; Invoice types record, and the Commit toggle finalizes.

Address Validation

Resolve Address Validates and normalizes a US or Canadian address, returning the USPS-standardized form, coordinates, resolution quality, and validation messages. The hygiene step that runs before tax math or record storage.

Companies

List Companies Retrieves the companies configured under the AvaTax account, each with the company code transactions are filed under. Supports filtering, ordering, and pagination. How multi-entity setups route transactions to the right books.

Tax Codes

List Tax Codes Retrieves the system-defined Avalara tax codes used to classify products and services, with filtering and pagination. The vocabulary for taxability mapping workflows.

Utilities

Ping Tests connectivity and verifies the account ID and license key, returning the API version and an authenticated flag. The pre-flight check agents run before production tax calculations.

Frequently Asked Questions

What can FlowRunner do with Avalara AvaTax?

FlowRunner agents can run Create Transaction, Resolve Address, and List Companies in Avalara AvaTax, plus 2 more actions.

Does connecting Avalara AvaTax to FlowRunner require OAuth?

No. Avalara AvaTax connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Avalara AvaTax trigger a FlowRunner workflow automatically?

Avalara AvaTax doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Avalara AvaTax

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us