DocuWriter.ai Trigger
AI-generatedOverview
This node acts as a webhook trigger for DocuWriter.ai events, specifically listening for generation-related events such as when a generation is created or updated. It is useful for automating workflows that need to respond to changes or new creations in document generations within DocuWriter.ai. For example, it can trigger a workflow to process or notify users when a new document generation is created or updated.
Use Case Examples
- Trigger a workflow when a new document generation is created to automatically archive or notify a team.
- Trigger a workflow when a document generation is updated to sync changes with another system or update a database.
Properties
| Name | Meaning |
|---|---|
| Event | The specific event that triggers the webhook, either 'generation.created' or 'generation.updated'. |
| Filter by Generation Type | A boolean flag to determine whether to filter incoming events by specific generation types. |
| Generation Types | A list of generation types to filter for when filtering is enabled. Only events matching these types will trigger the workflow. |
Output
JSON
event- The event type that triggered the webhook.timestamp- The timestamp when the event occurred or when the webhook was received.datauuid- The unique identifier of the generation.filename- The filename associated with the generation.generation_type- The human-readable generation type of the event.generated_by_user- The user who generated the document.updated_at- The timestamp when the generation was last updated.tag- Any tag associated with the generation.
Dependencies
- An API key credential for DocuWriter.ai to authenticate webhook events.
Troubleshooting
- If the webhook payload is missing required fields like 'event' or 'data', the node returns a 400 error indicating an invalid payload. Ensure the webhook source sends the correct data structure.
- If the event received does not match the configured event in the node, the webhook response will indicate the event was ignored. Verify the event configuration matches the expected webhook event.
- When filtering by generation type is enabled, if the incoming event's generation type is not in the selected list, the event is filtered out and the workflow is not triggered. Check the filter settings if expected events are not triggering workflows.