Events · Collections and folders
folder.created
Folder created
A folder was created in a collection.
- Object type
- folder
- Delivered to
- Endpoints that can see the object: by role, data profile and collections
Payload
idstringrequiredEvent ID (
evt_…), also sent as thewebhook-idheader. Use it to drop duplicate deliveries.typestringrequiredAllowed values:
folder.createdcreated_atstring (date-time)requiredWhen the change happened (UTC).
org_idintegerrequiredapi_versionstringrequiredContract version of the
dataschema.sequenceintegerDelivery sequence number within the endpoint (absent for a test event).
payloadstringrequiredthinmeans nodata: read the object through the API.Allowed values:
fullthindataobjectFields
actor_idinteger | nullrequiredThe user who performed the action;
nullfor an organization API key or the platform itself.
testbooleanrequiredA test event sent by
POST /v1/webhooks/{webhook_id}/test.
Example delivery
{
"id": "evt_0123456789abcdef0123456789abcdef",
"type": "folder.created",
"created_at": "2026-10-24T10:00:03Z",
"org_id": 1,
"api_version": "1.62.0",
"sequence": 1042,
"object": {
"type": "folder",
"id": "41"
},
"payload": "full",
"data": {
"folder": {
"id": "41",
"title": "Billing",
"collection": "support",
"collection_id": 3,
"parent_id": null,
"color": null,
"icon": null,
"metadata": {}
},
"actor_id": 7
},
"test": false
}Receiving events
Each delivery is a POST request with this JSON body to your endpoint. Verify the webhook-signature header (Standard Webhooks) before you trust the body, answer with a 2xx status within a few seconds, and do the work afterwards. Deliveries to one endpoint keep the order of events; a failed delivery is retried with growing pauses.
New event types and new fields can appear at any time: skip the types and fields you do not know.