Actions252
- Api Keys Actions
- Attachments Actions
- Blocklists Actions
- Calendar Channel Event Associations Actions
- Find Many Calendar Channel Event Associations
- Create One Calendar Channel Event Association
- Create Many Calendar Channel Event Associations
- Find One Calendar Channel Event Association
- Delete One Calendar Channel Event Association
- Update One Calendar Channel Event Association
- Find Calendar Channel Event Association Duplicates
- Companies Actions
- Calendar Channels Actions
- Calendar Event Participants Actions
- Calendar Events Actions
- Connected Accounts Actions
- Favorite Folders Actions
- Favorites Actions
- Message Channel Message Associations Actions
- Find Many Message Channel Message Associations
- Create One Message Channel Message Association
- Create Many Message Channel Message Associations
- Find One Message Channel Message Association
- Delete One Message Channel Message Association
- Update One Message Channel Message Association
- Find Message Channel Message Association Duplicates
- Message Channels Actions
- Message Folders Actions
- View Fields Actions
- Message Participants Actions
- Messages Actions
- Message Threads Actions
- Notes Actions
- Note Targets Actions
- Opportunities Actions
- People Actions
- Tasks Actions
- Task Targets Actions
- Timeline Activities Actions
- View Filter Groups Actions
- View Filters Actions
- View Groups Actions
- Views Actions
- View Sorts Actions
- Webhooks Actions
- Workflow Automated Triggers Actions
- Workflow Runs Actions
- Workflows Actions
- Workflow Versions Actions
- Workspace Members Actions
Overview
This node operation allows users to create multiple webhooks at once via the Twenty API. It is useful when you need to programmatically register several webhook endpoints in bulk, for example, to automate event handling or integrate with external services that send data via webhooks. Practical scenarios include setting up multiple webhook listeners for different events or environments without manually creating each one.
Properties
| Name | Meaning |
|---|---|
| Depth | Determines how much related nested information is included in the response: - 0: Only the primary webhook objects. - 1: Primary webhooks plus their directly related objects. - 2: Includes related objects of those related objects as well. |
| Body | JSON object representing the webhook(s) to create. This should contain the details of the webhook(s) according to the API specification. |
Output
The output json field contains the response from the API after creating the webhooks. Depending on the depth parameter, it includes the created webhook objects and optionally their related nested objects. The structure corresponds to the API's webhook resource representation.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Twenty API.
- The node uses the base URL provided by the user's credentials configuration.
- The request content type is JSON, so the node expects valid JSON input for the webhook body.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the node will fail to parse it. Ensure the JSON is correctly formatted.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
- API Response Errors: If the API rejects the webhook creation (e.g., due to invalid fields), the error message from the API will be returned. Check the webhook data against the API documentation.
- Depth Parameter Misuse: Using a depth value not supported by the API may result in unexpected responses or errors. Use only 0, 1, or 2 as specified.
Links and References
- Twenty API Documentation (Assumed official docs for webhook creation)
- n8n Documentation on Creating Webhook Nodes (for general webhook concepts)