App integrations

email

Connect Tolt to the platforms you already sell with

Use Plandalf to connect Tolt with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.

How it works

Plandalf is the commerce layer between apps

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

Pages this hub can feed

Product surfaces to check before wiring Tolt

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.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer setup before anything syncs

Tolt receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Follow-up starts from the purchase event

Tolt should get buyer, product, coupon, invoice, and offer context from the purchase event instead of a disconnected form submit.

The Numi integrations settings page showing Stripe, PayPal, TaxJar, and Avalara connection options.

Integration settings stay inspectable

Use the integrations surface to check Stripe, PayPal, TaxJar, Avalara, and test-mode routing before traffic hits a live checkout.

Feature detail