Actions111
- Item Actions
- Webhook Actions
- Collection Actions
- File Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Extension Actions
- Field Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node is designed to retrieve information about a specific webhook from a Directus v1 API instance. It is useful in scenarios where you need to fetch details of an existing webhook by its unique identifier, for example, to verify its configuration, audit its settings, or use its data in subsequent workflow steps.
Practical examples:
- Fetching the configuration of a webhook before updating it.
- Auditing webhook details as part of a monitoring workflow.
- Using webhook data to trigger conditional logic in your automation.
Properties
| Name | Meaning |
|---|---|
| ID | Primary key of the webhook. This is a required string value used to identify which webhook to retrieve. Example: 15 |
Output
The output will be a JSON object containing the details of the requested webhook. The exact structure depends on the Directus API response, but typically includes fields such as the webhook's ID, URL, event triggers, and status.
Dependencies
- Requires access to a Directus v1 API instance.
- May require authentication credentials (such as an API key or token) configured in n8n, depending on your Directus setup.
Troubleshooting
- Missing or invalid ID: If the provided ID does not correspond to an existing webhook, the node may return an error or an empty result. Ensure the ID is correct.
- Authentication errors: If credentials are missing or incorrect, you may receive authorization errors from the Directus API.
- Network issues: Connectivity problems between n8n and the Directus server can cause request failures.