member.lead_created
A member row was created as a lead.
When this fires
Somebody the project had never seen opened its bot, arrived through a Smart Link or a referral link, signed in to its portal or wrote to its support, and a member row was created for them with the status lead. It fires once per row, whichever door they came through, the moment the row is written; it never fires for a connected account adopted from a sibling project or linked by a backfill, because nobody just walked in. The lead sequences of Lead nurture enrol the member on the same event.
Caveats
- The payload carries no name and no connected account. Resolve the member with the member endpoint using
data.subscriber_id. - A lead who buys later raises
subscription.activated(a paid checkout) orsubscription.created(an access code or a cardless trial) with the samesubscriber_id; a lead who leaves without buying raises nothing more.
Related events
sequence.enrolled: the lead sequences the arrival enrols the member in, withtriggerlead.subscription.activated: the paid-checkout join signal.
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