Sequence playbook

Invoice issued record sync

Send invoice, customer, and payment records to email, CRM, and operations systems after checkout or renewal.

Triggers

invoice.issued
checkout.completed
subscription.renewed

Actions

email_invoice Email Invoice
sync_customer_record Sync Customer Record
notify_operations Notify Operations

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.

invoice.issued, checkout.completed, subscription.renewed 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.

email_invoice, sync_customer_record, notify_operations should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.

Integrations Purchase automations Postmark HubSpot Stripe

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 offer invoices screen showing invoice records. — Invoices preserve the commercial record after checkout so support and reporting are not guessing.

The Numi invoices records screen showing invoice line items and status. — Invoice records keep customer, line item, payment, and fulfillment context available after the sale.

The Numi offer editor invoices tab showing invoice email controls. — Invoice email settings belong with the offer so receipts match the purchase that created them.

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

The Numi offer editor automation tab showing sequence controls beside the checkout canvas. — Purchase automations start from the offer, product, buyer, payment, and invoice context Plandalf already knows.

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

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

Invoices

Feature

PDF invoices

Invoices

Feature