Overview
This node acts as a trigger for OpenProject events, starting an n8n workflow whenever specific OpenProject events occur. It listens to webhook calls from OpenProject and routes incoming event data to different outputs based on the event type. This is useful for automating processes that depend on project management activities such as project creation, updates, work package changes, time entries, or attachments.
Practical examples include:
- Automatically notifying a team chat when a new project or work package is created.
- Logging time entries into an external system when they are created in OpenProject.
- Triggering follow-up workflows when attachments are added to work packages.
Properties
| Name | Meaning |
|---|---|
| Activate Unmatched Output | Whether to send events that do not match any enabled event output to a dedicated "unmatched" output. |
| Event Outputs | Select which OpenProject event types should have dedicated outputs. Events not selected can be routed to unmatched if enabled. Options: Project Updated, Project Created, Work Package Updated, Work Package Created, Time Entry Created, Attachment Created. |
Output
The node dynamically creates multiple outputs based on the selected event types plus an optional unmatched output:
- Each enabled event type corresponds to one output. When an event of that type arrives, its data is sent to the matching output.
- If "Activate Unmatched Output" is enabled, events that do not match any selected event output are sent to the first output labeled "unmatched".
- The output data is an array of JSON objects containing:
body: The full webhook payload received from OpenProject.headers: HTTP headers from the webhook request.query: Query parameters from the webhook request.
No binary data is output by this node.
Dependencies
- Requires an active webhook URL configured in n8n to receive OpenProject event POST requests.
- No external API keys or credentials are directly handled by this node; it relies on OpenProject sending webhook events to the configured endpoint.
Troubleshooting
- Webhook URL Not Set: The node checks if the webhook URL exists but does not create or delete it automatically. Ensure the webhook URL is correctly set up in n8n and registered in OpenProject.
- No Events Received: Verify that OpenProject is configured to send webhooks to the correct URL and that the selected event outputs match the events being sent.
- Events Routed to Unmatched Output Unexpectedly: This happens if the event type is not among the selected event outputs. Either enable the unmatched output or add the missing event type to the selection.
- Empty Outputs: If no event outputs are selected and unmatched output is disabled, the node will not emit any data.