Overview
This node acts as a webhook trigger for Outline events. It listens to various event types from the Outline service, such as document creation, updates, deletions, and user or collection changes. When one of the selected events occurs in Outline, the node receives the webhook payload and triggers the workflow.
Common scenarios include automating workflows based on content changes in Outline, such as syncing documents to other systems when created or updated, notifying teams about user or collection changes, or archiving data when documents are deleted.
For example, you could use this node to:
- Trigger a notification workflow whenever a new document is created.
- Automatically update a search index when documents are updated or restored.
- Sync user information when users are created or updated in Outline.
Properties
| Name | Meaning |
|---|---|
| Events | The specific Outline events to listen for. Multiple options can be selected: |
| - Document Created: Triggers when a document is created | |
| - Document Updated: Triggers when a document is updated | |
| - Document Deleted: Triggers when a document is deleted | |
| - Document Archived: Triggers when a document is archived | |
| - Document Restored: Triggers when a document is restored | |
| - Collection Created: Triggers when a collection is created | |
| - Collection Updated: Triggers when a collection is updated | |
| - Collection Deleted: Triggers when a collection is deleted | |
| - User Created: Triggers when a user is created | |
| - User Updated: Triggers when a user is updated |
Output
The node outputs the JSON payload received from the Outline webhook event. This payload contains detailed information about the event that occurred, including the event name and associated data (e.g., document details, user info).
The output structure is:
{
"json": {
// Full webhook event data from Outline
}
}
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Outline API.
- The node depends on the Outline API to register, verify, and delete webhooks.
- The workflow must be accessible via a public URL to receive webhook calls from Outline.
Troubleshooting
- No events selected: If no events are selected in the node properties, the webhook will not filter any events and will pass all incoming webhook data through.
- Webhook registration failure: Errors during webhook creation usually indicate invalid credentials or network issues. Verify the API key and ensure the n8n instance is reachable from Outline.
- Webhook not triggering: Ensure the workflow is active and the webhook URL is publicly accessible. Also, confirm that the selected events match those sent by Outline.
- Permission errors: The API key used must have permissions to manage webhooks in Outline.