Overview
This node acts as a webhook trigger for DocuWriter.ai events, specifically listening for generation-related activities. It triggers workflows when a new generation is created or an existing generation is updated within DocuWriter.ai. This is useful for automating processes that depend on document generation events, such as notifying teams, updating databases, or further processing generated content.
Practical examples include:
- Automatically starting a review process when a new documentation generation is completed.
- Syncing updated generation metadata to other systems when a generation is modified.
- Filtering and reacting only to specific types of generations, e.g., documentation or release notes.
Properties
| Name | Meaning |
|---|---|
| Event | The event that should trigger this webhook. Options: "Generation Created" (when a new generation is created), "Generation Updated" (when a generation is updated). |
| Filter by Generation Type | Whether to filter incoming events by specific generation types. Boolean value: true or false. |
| Generation Types | The specific generation types to filter for if filtering is enabled. Multiple selection allowed. Options include various generation categories like "[Basic] => Documentation", "[Git] => Release Notes", "[Basic] => Tests", etc. |
Output
The node outputs JSON data representing the event details when triggered. The structure includes:
event: The event type string (e.g., "generation.created").timestamp: The timestamp of the event or the current time if not provided.data: An object containing key information about the generation:uuid: Unique identifier of the generation.filename: Name of the generated file.generation_type: The human-readable generation type name (mapped from internal codes).generated_by_user: User who initiated the generation.updated_at: Timestamp of the last update.tag: Any associated tag with the generation.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with DocuWriter.ai.
- Needs to be configured with a webhook URL accessible by DocuWriter.ai to receive event POST requests.
- No additional external dependencies are indicated.
Troubleshooting
- Invalid webhook payload: If the incoming webhook does not contain expected
eventordatafields, the node responds with a 400 error. Ensure DocuWriter.ai sends correctly structured payloads. - Event ignored: If the event received does not match the configured event in the node settings, it will ignore the webhook with a 200 response. Verify the event type configuration matches the intended trigger.
- Generation type filtered out: When filtering by generation type is enabled but the incoming generation's type is not in the selected list, the webhook is ignored. Check that the correct generation types are selected.
- Webhook accessibility: Make sure the webhook endpoint is publicly reachable by DocuWriter.ai; otherwise, no events will be received.
Links and References
- DocuWriter.ai official website (for understanding event types and generation concepts)
- n8n Webhook Trigger Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/