Sequence playbook

Price plan changed lifecycle

Route product, price, plan, and subscription changes into lifecycle messaging and internal records.

Triggers

price.changed
subscription.created
subscription.updated

Actions

sync_plan_record Sync Plan Record
start_lifecycle_segment Start Lifecycle Segment
notify_team Notify Team

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.

price.changed, subscription.created, subscription.updated 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.

sync_plan_record, start_lifecycle_segment, notify_team should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.

Integrations Purchase automations Stripe Customer.io HubSpot

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 editor products panel showing products attached to an offer. — Product records tell the sequence what was purchased, granted, invoiced, or upgraded.

The Numi pricing table showing configured offer prices. — Price records let lifecycle sequences react to plan changes without parsing a checkout note.

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.

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

Products

Products and pricing

Feature

Product variants

Products and pricing