Delivery headers
When folk sends a webhook delivery, it will include the following special headers:webhook-id: The unique identifier of the webhook event.webhook-timestamp: The timestamp of the webhook delivery.webhook-signature: The signature used to verify the authenticity of the webhook delivery. For more information, see validating webhook deliveries.
Payload format
folk webhooks send a thin payload with only the necessary information to identify the resource that the event occurred on, and based on the event type, it can optionally include the attributes that changed. The payload of the webhook delivery is a JSON object that will always contain the following fields:The unique identifier of the webhook event.
The event type that occurred.
The date and time the event occurred, in ISO 8601 format.
The API URL of the webhook that delivered the event.
The data of the webhook delivery. It contains the properties that help identify the resource that the event occurred on.
Delivery example
Delivery example
Event list
Person events
person.created
person.created
This event occurs when a person is created in the workspace.Example:
person.updated
person.updated
This event occurs when a person’s native attributes or custom fields are updated.Example:
The
description value is never included in the payload.person.deleted
person.deleted
This event occurs when a person is deleted from the workspace.Example:
person.groups_updated
person.groups_updated
This event occurs when a person’s groups are updated.Example:
person.workspace_interaction_metadata_updated
person.workspace_interaction_metadata_updated
This event occurs when a person’s workspace interaction metadata is updated.Example:
Company events
company.created
company.created
This event occurs when a company is created in the workspace.Example:
company.updated
company.updated
This event occurs when a company’s native attributes or custom fields are updated.Example:
The
description value is never included in the payload.company.deleted
company.deleted
This event occurs when a company is deleted from the workspace.Example:
company.groups_updated
company.groups_updated
This event occurs when a company’s groups are updated.Example:
Deal events
object.created
object.created
This event occurs when a deal is created in the workspace.Example:
object.updated
object.updated
This event occurs when a deal is updated in the workspace.Example:
object.deleted
object.deleted
This event occurs when a deal is deleted from the workspace.Example:
Note events
note.created
note.created
This event occurs when a note is created in the workspace.Example:
note.updated
note.updated
This event occurs when a note is updated in the workspace.Example:
The
content value is never included in the payload.note.deleted
note.deleted
This event occurs when a note is deleted from the workspace.Example:
Reminder events
reminder.created
reminder.created
This event occurs when a reminder is created in the workspace.Example:
reminder.updated
reminder.updated
This event occurs when a reminder is updated in the workspace.Example:
reminder.deleted
reminder.deleted
This event occurs when a reminder is deleted from the workspace.Example:
reminder.triggered
reminder.triggered
This event occurs when a reminder is triggered in the workspace.Example:
Filtering events
Through the API, it is also possible to add filters to events in order to narrow down the notifications you receive. Filters allow you to achieve advanced workflow capabilities, such as:- Only receive notifications when a person is added to a specific group.
- Only receive notifications when a company is moved to a specific pipeline status.
- Only receive notifications when a deal from a specific group is updated.