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 interacts with the Twenty API to retrieve detailed information about a specific webhook by its unique identifier. It is useful when you need to fetch the configuration or status of a particular webhook previously set up in the Twenty system. For example, you might use this node to verify webhook details before processing events or to audit webhook configurations programmatically.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the webhook object you want to retrieve. |
| Depth | Determines how much related nested data to include in the response: |
| - 0: Only the primary webhook object information. | |
| - 1: The webhook plus its directly related objects (no further nesting). | |
| - 2: The webhook, its directly related objects, and their related objects (two levels deep). |
Output
The node outputs JSON data representing the webhook object identified by the provided Id. Depending on the selected depth, the output includes nested related objects to varying degrees, providing comprehensive details about the webhook and its associations. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating requests to the Twenty API.
- The node uses the base URL configured via credentials to connect to the Twenty API endpoint.
- No additional external dependencies are needed beyond the API access.
Troubleshooting
- Invalid Id Error: If the provided webhook Id does not exist or is malformed, the node will likely return an error indicating the object was not found. Verify the Id value is correct.
- Authentication Failures: Ensure that the API key credential is valid and has sufficient permissions to read webhook data.
- Depth Parameter Issues: Providing an unsupported depth value may cause unexpected results or errors. Use only 0, 1, or 2 as specified.
- Network or API Errors: Check network connectivity and API service status if requests fail unexpectedly.
Links and References
- Twenty API Documentation (Assumed official API docs for reference)
- n8n Documentation on Using API Credentials