Offer configuration stays visible
Use Offers to decide what Tolt 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 Tolt receives checkout, payment, tax, or workflow context.
Use Offers to decide what Tolt receives: product, price, buyer, checkout mode, invoice, and automation context.
Before Tolt enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Tolt should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
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 Tolt 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 Tolt should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when Tolt 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.
Tolt runs affiliate and referral programs for SaaS merchants. Their default integration listens to Stripe webhooks and credits commissions when a referred customer pays — but Plandalf checkouts use raw PaymentIntents from Stripe Elements, so the resulting Stripe charge has no line items for Tolt’s product matcher to walk.
app/Apps/Tolt/ contains a Saloon-based
handler with FindOrCreateCustomer and CreateTransaction actions
that talk directly to Tolt’s REST API. Wire them on the invoice.paid
trigger and Tolt receives one transaction per invoice line item.CreateTransaction posts a transaction
per item with charge_id {invoice_id}-{item_id}, so multi-product
carts award commissions correctly without collapsing into a single
charge record.window.tolt_data from
the visitor’s affiliate cookie onto checkout_sessions.properties
so the action has the partner / click context at trigger time.tolt_data on the session. No noise in Tolt’s
dashboard from organic checkouts.specs/affiliates/ territory.invoice.paid.Automation graph
How Tolt participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
tolt.custom_api_calltrigger: plandalf.checkout.completed
actions:
- tolt.custom_api_call:
endpoint: /v1/event
payload:
email: ${customer.email}
plan: ${product_slug}Pair it with
Platforms whose roles complement Tolt inside a Plandalf sequence.
Tolt + HubSpot
Coordinate paid + lifecycle by sharing audiences between Tolt and HubSpot.
Tolt + ActiveCampaign
Compose Tolt and ActiveCampaign programmatically via the Plandalf SDK.
Tolt + beehiiv
Compose Tolt and beehiiv programmatically via the Plandalf SDK.
Tolt + Kit (ConvertKit)
Compose Tolt and Kit (ConvertKit) programmatically via the Plandalf SDK.
Tolt + Customer.io
Compose Tolt and Customer.io programmatically via the Plandalf SDK.
Tolt + Drip
Compose Tolt and Drip programmatically via the Plandalf SDK.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use Tolt with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
For anything not covered by a native trigger, configure a Tolt webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/tolt \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d @event.jsonFAQ
Plandalf itself is free to connect to Tolt. You only need a Tolt account that allows API access, which is almost every paid plan.
Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Tolt'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 Tolt plus a log of events Plandalf fired. Source-of-truth data stays in Tolt.
Use the generic `tolt.custom_api_call` action or the inbound `tolt.webhook` trigger. Anything Tolt's REST API can do, a Plandalf sequence can drive.
Plandalf respects Tolt's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
Tolt's homepage at https://tolt.com links to their developer docs. For Plandalf-side questions about the Tolt integration, see the Plandalf docs.