Offer configuration stays visible
Use Offers to decide what TaxJar receives: product, price, buyer, checkout mode, invoice, and automation context.
Product surfaces
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before TaxJar receives checkout, payment, tax, or workflow context.
Use Offers to decide what TaxJar receives: product, price, buyer, checkout mode, invoice, and automation context.
Before TaxJar enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
TaxJar should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
TaxJar belongs in the checkout calculation path, not as cleanup after invoices and payment records drift apart.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair TaxJar with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when TaxJar should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when TaxJar belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
US-and-Canada-focused sales tax automation. Connect with an API token from your TaxJar dashboard. We compute tax on every checkout in your covered jurisdictions, push transactions back for filing, and cache exempt-customer rules per org.
Automation graph
How TaxJar participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
trigger: plandalf.checkout.tax_quote_requested
actions:
- taxjar.calculate_tax:
address: ${customer.address}
lineItems: ${cart.items}Pair it with
Platforms whose roles complement TaxJar inside a Plandalf sequence.
TaxJar + PayPal
Calculate sales tax / VAT on every PayPal charge.
TaxJar + Stripe
Calculate sales tax / VAT on every Stripe charge.
TaxJar + ActiveCampaign
Compose TaxJar and ActiveCampaign programmatically via the Plandalf SDK.
TaxJar + beehiiv
Compose TaxJar and beehiiv programmatically via the Plandalf SDK.
TaxJar + Kit (ConvertKit)
Compose TaxJar and Kit (ConvertKit) programmatically via the Plandalf SDK.
TaxJar + Custom API
Compose TaxJar and Custom API programmatically via the Plandalf SDK.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use TaxJar with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
TaxJar doesn't expose a recognized capability above, so wire it up through the Plandalf REST API — POST events in, GET state out.
curl -X POST https://api.plandalf.com/v1/events \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d '{"source": "taxjar", "type": "custom", "data": {}}'FAQ
Plandalf itself is free to connect to TaxJar. You only need a TaxJar account that allows API access, which is almost every paid plan.
Under 10 minutes — paste a webhook URL into TaxJar, point it at the Plandalf endpoint, and trigger a test event to confirm.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and TaxJar's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the minimum IDs needed to address a record in TaxJar plus a log of events Plandalf fired. Source-of-truth data stays in TaxJar.
Drop into the Plandalf REST API and call TaxJar directly from your sequence's HTTP action. Anything TaxJar's public surface exposes is reachable.
There's no Plandalf-side limit. TaxJar's own plan limits apply.
TaxJar's homepage at https://www.taxjar.com links to their developer docs. For Plandalf-side questions about the TaxJar integration, see the Plandalf docs.