Sequences

Everything that happens after the sale, on autopilot.

A sequence is a chain of actions that fires on a checkout event. Grant access, send the receipt, recover the failed payment, sync the CRM, pay the affiliate — wired to the tools you already use, with no glue code.

Start building See it inside Offers →

13 triggers 12 action types 40+ integrations

app.plandalf.com/sequences

Course Checkout receipt

Emails the buyer their receipt and notifies the team

On

Linked offers

Course Checkout×

Tested

1

Trigger · Plandalf

Checkout completed

When an offer checkout finishes

Not tested

2

Action · Postmark

Send receipt email

To the customer

Needs setup

3

Action · HubSpot

Add contact to HubSpot

Tag as a customer

Builder paths

Choose the post-purchase job before choosing the app.

Sequences should read like implementation recipes: start from the checkout event, keep the offer context, then choose whether the next step is fulfilment, recovery, webhook fanout, CRM sync, affiliate work, tax cleanup, or a lifecycle message.

The Numi offer editor automation tab showing attached sequences.

Fulfil the first purchase

Start with the checkout completed event, then grant access, send a receipt, create invoice records, alert the team, and pass the buyer into the right support or CRM flow.

Checkout completed fulfillment Hosted checkout Purchase automations Invoices Postmark HubSpot

The Numi coupon expiration panel connected to a deadline.

Recover or save a stalled buyer

Use checkout started, coupon expiry, failed payment, or deadline expired events to send a reminder, apply a save offer, update the CRM, and stop the promo when the timer ends.

Abandonment recovery Deadline save offer Timers Coupons Save offer sequence Email countdown GIFs

The Numi API documentation surface with endpoint navigation.

Fan out to a developer stack

Use one purchase event as the source, then fan it into webhooks, SDK apps, analytics, custom fulfilment, tax records, and backend jobs with the full offer context intact.

Webhook fanout sequence Webhook docs API reference SDK checkout Developer webhook stack Custom API

The Numi invoices index with payment, invoice, and customer rows.

Keep records clean after money moves

Use invoice issued, refund created, affiliate sale, and tax reconciliation events to keep finance records, customer history, and connected accounting tools aligned.

Invoice record sync Affiliate tax reconciliation Invoices Affiliate integration Tax settings Avalara

The combinatorics

One event in. Anything out.

Pick any trigger. Route it through the engine. Land it in any app — or several. The same three slots produce thousands of distinct automations before you've even chained a second step.

checkout.completed
payment.succeeded
payment.failed
cart.abandoned
upsell.accepted
upsell.declined

Sequence
engine

Filter, wait, branch,
retry, fan out

13 triggers × 12 actions × 40 apps

6,240 single-step automations. Chain the steps and the number stops mattering.

Triggers

It starts with an event.

Every meaningful moment in the buying lifecycle is an event you can listen for — from the first abandoned cart to a renewal three years later.

checkout.completed
Checkout completed

A buyer finished paying for an offer.
payment.succeeded
Payment succeeded

A charge cleared — including renewals.
payment.failed
Payment failed

A card was declined or a charge bounced.
cart.abandoned
Cart abandoned

Someone started checkout but never paid.
upsell.accepted
Upsell accepted

A buyer added a post-purchase upsell.
upsell.declined
Upsell declined

A buyer skipped the upsell offer.
bump.accepted
Order bump accepted

A one-click add-on was taken at checkout.
coupon.redeemed
Coupon redeemed

A discount code was applied to an order.
subscription.created
Subscription started

A recurring plan began.
subscription.cancelled
Subscription cancelled

A buyer ended their plan.
invoice.paid
Invoice paid

A recurring or one-off invoice settled.
refund.issued
Refund issued

Money was returned to a buyer.
trial.ending
Trial ending

A free trial is about to convert.

Actions

Then it does the work.

Each step can do one thing in one tool. Stack them, add a wait, branch on what the buyer actually chose — the sequence carries the full order context the whole way down.

Grant product access

Provision a course, membership, or license.
Send a receipt

Email the buyer a branded confirmation.
Start an onboarding flow

Drop the buyer into a welcome sequence.
Recover a failed payment

Retry the charge and email the buyer.
Recover an abandoned cart

Nudge people who never finished.
Update your CRM

Tag the contact and move the deal.
Alert the team

Open a conversation on a high-ticket sale.
Pay an affiliate

Credit the referral commission.
Enrol in a promo

Add the buyer to a running campaign.
Call a webhook

POST the event to any endpoint you own.
Run a custom API request

Hit your own backend with the order data.
Wait, then branch

Pause, check a condition, take a different path.

The builder

This is the real thing, not a diagram.

Every sequence lives in one place: triggers, actions, scheduled runs, integrations, webhooks, and a live event count so you can see exactly what fired and when.

app.plandalf.com/sequences

Automation

Sequences that react to events — triggers, actions, and scheduled runs.

MarketplaceTemplatesMy SequencesMy apps

Search sequences...

AllRecoveryFulfilment

Checkout receipt

Emails the buyer their receipt the moment checkout completes.

→

412 events →

Active

Abandoned cart recovery

Reaches out to customers who started checkout but didn't pay.

→

38 events →

Active

Failed payment dunning

Untested

Retries and emails when a charge is declined.

→

0 events →

Inactive

CRM sync

Sends the buyer to your CRM on purchase.

→

121 events →

Active

New customer alert

Setup

Opens a conversation in Intercom for high-ticket orders.

→

6 events →

Inactive

Tolt referral payout

Credits affiliates in Tolt when an invoice is paid.

→

14 events →

Active

Product context

The sequence is only useful if it knows what happened in the sale.

These screenshots show the product surfaces a sequence should stay connected to: hosted checkout, Offers, Timers, purchase automations, API docs, webhooks, and integration handoffs.

The Numi hosted checkout product surface where a buyer completes checkout.

Checkout event source

Sequences start from the checkout, payment, product, price, coupon, and buyer context already captured by Offers.

The Numi offer editor automation tab connected to a sale.

Offer automation tab

Use purchase automations when the work belongs next to the Offer: grant access, notify a team, or trigger a webhook.

The Numi deadline campaign product surface.

Deadline and promo context

Timers can carry the deadline, coupon, launch window, and expiry state that a sequence needs after the sale.

The Numi API docs and developer implementation surface.

API-first handoff

Use API docs and webhooks when a sequence needs to hand purchase events to a custom app, SDK, or backend workflow.

The Numi offer invoice records view with customer rows and payment state.

Invoice and record context

Invoices, receipts, refunds, payment state, and buyer records give the sequence an auditable source of truth after checkout.

The Numi automation integrations surface with connected app destinations.

Integration destination

Integration destinations keep the CRM, email tool, support queue, affiliate app, tax tool, or custom API one step away from the sale.

The Numi API key settings surface for developer handoff.

API keys and SDK handoff

API keys, SDK checkout, and webhooks let a developer or agent connect purchase events to a backend without rebuilding checkout.

Subscription lifecycle

Subscription price changes, renewals, failed payments, and cancellations become lifecycle triggers instead of disconnected support chores.

The Numi promo email GIF settings surface.

Promo and deadline branch

Coupons, email countdown GIFs, deadline campaigns, and save offers can branch the sequence based on the buyer deadline state.

Recipes

Sequences teams run today.

A small slice of what people wire up in the first afternoon. Each one is a trigger and a short chain of apps — copy it, then make it yours.

Course access + receipt
Fulfilment
checkout.completed
Grant the course, email the receipt, ping the team.
Abandoned cart recovery
Recovery
cart.abandoned
Wait an hour, then email the buyer who never paid.
Failed payment dunning
Recovery
payment.failed
Retry the charge, then email if it still declines.
CRM lifecycle sync
Ops
checkout.completed
Create the contact and move the deal to Won.
Affiliate payout
Revenue
invoice.paid
Credit the referrer the moment the invoice settles.
High-ticket alert
Ops
checkout.completed
Open an Intercom conversation on big orders.
Upsell → onboarding
Revenue
upsell.accepted
Provision the add-on and start its own welcome flow.
Trial conversion push
Revenue
trial.ending
Warn the buyer and offer a save coupon before renewal.
New member welcome
Fulfilment
subscription.created
Add to the member list and send the welcome pack.
Cancellation win-back
Recovery
subscription.cancelled
Tag the churned buyer and start a win-back drip.
Refund cleanup
Ops
refund.issued
Revoke access and update the CRM record.
Webhook to your stack
Ops
checkout.completed
POST the full order to your own fulfilment service.

Integrations

Wire any step to the tools you already pay for.

40+ integrations out of the box, plus webhooks and an open API for the long tail. A sequence step can land in any of them — and Plandalf carries the full order context the whole way.