Tolt

Integration

Tolt

Send attributed purchase transactions to Tolt when a checkout invoice is paid.

What it does

Product surfaces

Where Tolt fits in the buying workflow

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.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Tolt should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Builder paths

Stack guides that use Tolt

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

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 integrationapp/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 attributionCreateTransaction 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.

Automation graph

Connecting Tolt

How Tolt participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Tolt

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

tolt.webhook
Fires when Tolt POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on Tolt

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

tolt.custom_api_call
Hit any Tolt REST endpoint with a templated payload.
Example sequence
trigger: plandalf.checkout.completed
actions:
  - tolt.custom_api_call:
      endpoint: /v1/event
      payload:
        email: ${customer.email}
        plan: ${product_slug}

Integration methods

How Tolt connects to Plandalf

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.

  1. Method 1

    REST API webhook

    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.json
Official Tolt docs and sign-up: tolt.com

FAQ

Common questions about the Tolt integration

Do I need a paid plan to use Tolt with Plandalf?

Plandalf itself is free to connect to Tolt. You only need a Tolt account that allows API access, which is almost every paid plan.

How long does setup take?

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.

Can I disconnect Tolt later without losing data?

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.

Does Plandalf store Tolt data?

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.

What if my marketing need isn't covered by the actions or triggers listed here?

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.

Is there a usage limit?

Plandalf respects Tolt's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find Tolt's own documentation?

Tolt's homepage at https://tolt.com links to their developer docs. For Plandalf-side questions about the Tolt integration, see the Plandalf docs.

Feature detail