Sequence playbook

Purchase event webhook fanout

Fan a single purchase event out to custom APIs, SDK-built apps, email systems, analytics, and fulfillment services.

Triggers

purchase.completed
payment.succeeded

Actions

send_webhook Send Webhook
grant_entitlement Grant Entitlement
track_conversion Track Conversion
sync_metadata Sync Metadata

Implementation

How this sequence should be wired.

A named sequence is useful only when the trigger, commercial context, and downstream handoff are all explicit across checkout, integrations, webhooks, and fulfillment.

Trigger

Choose the event that starts the work.

purchase.completed, payment.succeeded should fire from a real Plandalf checkout, payment, invoice, subscription, deadline, or affiliate event, not from a front-end success page alone.

Automations Sequences Webhooks

Context

Carry the commercial state with the event.

The sequence should know the offer, product, price, buyer, payment state, coupon, invoice, and integration context before it touches another tool.

Offers Products Prices Invoices

Handoff

Route each action to the right product or platform.

send_webhook, grant_entitlement, track_conversion, sync_metadata should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.

Integrations Purchase automations Custom API React Postmark

Product surfaces

Where the operator checks the work.

These are real Plandalf app surfaces tied to the products, features, integrations, invoices, payment settings, API docs, and sequences this playbook depends on.

The Numi API keys settings page used to create organization API keys. — API keys and webhooks are the bridge when the purchase event needs to reach a custom app.

The Numi Developer API documentation with sidebar navigation and SDK method reference. — SDK docs own implementation details once the sequence playbook has defined the business path.

The Numi automation integrations screen showing connected tools. — Integrations decide where the event lands after Plandalf records the checkout state.

The Numi offer editor automation tab showing sequence controls beside the checkout canvas. — Automation is configured beside the offer so the purchase event stays attached to the buying surface.

The Numi sequences screen showing automated workflow configuration. — Sequences turn checkout, payment, invoice, subscription, and deadline events into follow-up work.

The Numi offer invoices screen showing invoice records. — Invoices preserve the commercial record after checkout so support and reporting are not guessing.

Reference links

Everything this playbook touches.

Use these links when a builder needs to move from the sequence concept into the exact product, feature, integration, platform, workflow, stack, or documentation page.

Product

Offers

The checkout surface where your customers actually decide.

Product

Automations

The work that happens after a customer buys.

Feature

API

Developer/API

Feature

SDK

Developer/API