creator_task.* events
A hand-arranged perk a subscriber bought becomes a task for the creator, and is done.
A hand-arranged perk a subscriber bought becomes a task for the creator, and is done. A creator task is a grant no connector can give: a manual resource (a perk you hand over yourself: a file, a call, a seat in a place no bot manages). When a purchase entitles a subscriber to one, the access ledger records a creator_task grant and opens a task for the creator; when the creator marks it done, the grant is issued and the subscriber's access is announced like any other.
Background
Example envelope
{
"id": "evt_01HX...",
"type": "creator_task.opened",
"created_at": "2026-09-12T10:05:30Z",
"api_version": "2026-05-01",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"data": {
"task_id": "9e4b2c71-3d58-4a6f-b0e2-7c1d5f8a9b34",
"grant_id": "7d1c3e9a-2b64-4f0e-9a58-3c6b1d8e2f47",
"subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",
"subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
"resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",
"resource_kind": "manual",
"instructions": "Give Ada Lovelace access to Welcome packet.",
"due_at": null
}
}Required ability
Tokens subscribing to creator_task.* events must carry project-subscription:view at mint time.
Events
creator_task.openedA purchase entitles a subscriber to a manual perk, so the creator has something to do by hand.creator_task.completedThe creator marked a manual perk as handed over; the grant is issued.creator_task.opened
WEBHOOKA purchase entitles a subscriber to a manual perk, so the creator has something to do by hand.
When this fires
A subscription becomes active (or a pass window opens) on a plan that includes a manual resource: a perk no connector can give, which the creator hands over themselves. The access ledger records a creator_task grant in state pending and opens a task naming the member and the perk; this event carries that task. One event per manual resource the purchase entitles the member to. Nothing is sent to the member by a bot for a manual perk; the portal shows the perk as arranged by the organiser.
Caveats
- A task is opened once per purchase, resource and window; a retry of the granting job does not open a second one.
- A purchase that ends before the task is done revokes the grant; the task then drops out of the open list without a
creator_task.completed.
Related events
creator_task.completed: the task is done and the grant issued.member.resource_added: raised for the samegrant_idon completion.
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.
creator_task.completed
WEBHOOKThe creator marked a manual perk as handed over; the grant is issued.
When this fires
The creator (or a teammate, an integration or an agent on their behalf) marks a creator task done: on the members page, through the complete endpoint or the MCP tool complete_creator_task. The access ledger row moves from pending to granted, this event says who did it, and member.resource_added follows for the same grant_id with mode creator_task.
Caveats
- Completing a task is not idempotent over the API: a second call for a completed task answers
422 VALIDATION_FAILED. - The member is not messaged by a bot on completion; tell them yourself, or let the portal show the perk as delivered.
Related events
creator_task.opened: the task being done.member.resource_added: raised for the same grant on completion.
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.
Related
How is this guide?