A member entered a recovery sequence.
When this fires
The sequence's trigger fired for a member of the project and nothing stood in the way. For churned that is member.churned: the member's last live membership ended, through its end date, a cancellation that ran out or the close of a failed-payment grace window. For lead it is member.lead_created; for stalled_checkout the hourly sweep's checkout.stalled; for trial_ending the hourly trial sweep, once a trial without a card is within the project's lead time of its end. The member is enrolled into every running sequence on that trigger, once each, provided the sequence has at least one step, the member holds nothing the trigger counts as a conversion (any live membership, or for trial_ending a paid one), they have not asked the project's sequences to stop, they are not already part-way through that sequence, and the project owner's plan includes sequences. next_due_at is the moment of the trigger plus the first step's delay; the step goes out on the first hourly sweep after it.
Caveats
- A member who buys again before the first step is due never receives it: the sweep finds them holding a live membership and ends the passage as sequence.converted instead.
- A sequence switched off between the trigger and the first step lets the member go as sequence.exited with the reason disabled.
Related events
- member.churned: the churn trigger.
- sequence.step_sent: the steps that follow.
- sequence.converted: how a passage ends well.
- sequence.exited: how a passage ends otherwise.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.