sequence.enrolled
A member entered a win-back 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. The member is enrolled into every running sequence on that trigger, once each, provided the sequence has at least one step, the member holds no other live membership in the project, 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.convertedinstead. - A sequence switched off between the trigger and the first step lets the member go as
sequence.exitedwith the reasondisabled.
Related events
member.churned: the trigger behind every enrolment today.sequence.step_sent: the steps that follow.sequence.converted: how a passage ends well.sequence.exited: how a passage ends otherwise.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on