Offer setup before anything syncs
Tolt receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.
App integrations
Use Plandalf to connect Tolt with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.
Popular connections
Use these as practical recipes, not just directory entries. Each one should explain the checkout, automation, payment, email, CRM, tax, or API handoff that matters.
Tolt + PayPal
Score 35
Use Tolt and PayPal together in a Plandalf checkout and post-purchase workflow.
Tolt + Drip
Score 30
Use Tolt and Drip together in a Plandalf checkout and post-purchase workflow.
Tolt + HubSpot
Score 30
Use Tolt and HubSpot together in a Plandalf checkout and post-purchase workflow.
Tolt + Kit (ConvertKit)
Score 30
Use Tolt and Kit (ConvertKit) together in a Plandalf checkout and post-purchase workflow.
Tolt + Klaviyo
Score 30
Use Tolt and Klaviyo together in a Plandalf checkout and post-purchase workflow.
Tolt + Mailchimp
Score 30
Use Tolt and Mailchimp together in a Plandalf checkout and post-purchase workflow.
Tolt + Zapier
Score 30
Use Tolt and Zapier together in a Plandalf checkout and post-purchase workflow.
Tolt + Avalara
Score 27
Use Tolt and Avalara together in a Plandalf checkout and post-purchase workflow.
Tolt + Stripe
Score 27
Use Tolt and Stripe together in a Plandalf checkout and post-purchase workflow.
Tolt + TaxJar
Score 27
Use Tolt and TaxJar together in a Plandalf checkout and post-purchase workflow.
Tolt + Next.js
Score 24
Use Tolt and Next.js together in a Plandalf checkout and post-purchase workflow.
Tolt + Shopify
Score 24
Use Tolt and Shopify together in a Plandalf checkout and post-purchase workflow.
How it works
Tolt keeps doing what it is best at. Plandalf handles the offer, checkout, buyer fields, payment context, invoice data, and post-purchase events that every other app needs.
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. ## What Plandalf does here - **Automation integration** — `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. - **Per-line attribution** — `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. - **Click-id passthrough** — the SDK forwards `window.tolt_data` from the visitor's affiliate cookie onto `checkout_sessions.properties` so the action has the partner / click context at trigger time. - **Auto-skip when no affiliate** — both actions short-circuit cleanly when there's no `tolt_data` on the session. No noise in Tolt's dashboard from organic checkouts. ## What Plandalf does *not* do - We do not replace Tolt. We don't run our own affiliate program out of this integration; that's `specs/affiliates/` territory. - We do not consume Tolt's webhooks. The flow is one-way: Plandalf → Tolt at `invoice.paid`.
Search paths
A useful Tolt integration page should show where the operator configures Offers, payment options, invoices, Automations, integrations, and API settings before a developer ships the flow.
Tolt receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.
Tolt should get buyer, product, coupon, invoice, and offer context from the purchase event instead of a disconnected form submit.
Tolt can be part of a payment stack, a site stack, a marketing stack, or an automation stack. These Plandalf resources keep the implementation tied to real checkout and purchase events.