Overview
This node acts as a webhook trigger for Reportei events, allowing workflows in n8n to respond automatically when specific events occur within the Reportei platform. It subscribes to various event types related to projects (clients) in Reportei and listens for incoming webhook calls triggered by those events.
Common scenarios where this node is beneficial include:
- Automating notifications or follow-up actions when a new report is created.
- Triggering workflows when dashboards are created or milestones are added.
- Responding to control goal achievements or automation executions within Reportei projects.
For example, you could use this node to start a workflow that sends a Slack message whenever a "Report Created" event happens in a selected project, or update a CRM system when a timeline milestone is added.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | Select the Reportei project (client) to which you want to add the trigger. You can choose from a list of available projects or specify an ID using an expression. |
| Event Type | The type of Reportei event to subscribe to. Options include: Automation Executed, Control Goal Met, Control Goal Not Met, Dashboard Created, Report Created, Timeline Milestone Added. |
| Custom Webhook Base URL | Optional. If your n8n instance is behind a tunnel or requires a specific public domain, provide the base URL here. This replaces the default localhost address in the webhook URL with the specified domain. |
Output
The node outputs data received from the Reportei webhook as JSON in the json field of the output item. The structure corresponds directly to the webhook payload sent by Reportei for the subscribed event.
Example output structure:
{
"json": {
// The full webhook payload from Reportei for the event
}
}
No binary data output is produced by this node.
Dependencies
- Requires an API authentication credential for Reportei to subscribe/unsubscribe webhooks.
- Needs network accessibility for receiving incoming webhook POST requests at the generated webhook URL.
- Optionally requires configuration of a public-facing URL if running n8n behind tunnels or firewalls (via the "Custom Webhook Base URL" property).
Troubleshooting
- Webhook subscription failure: Ensure the provided API credential has sufficient permissions and the project ID is valid.
- Webhook not triggering: Verify that the webhook URL is publicly accessible and correctly registered in Reportei. If behind a tunnel, set the "Custom Webhook Base URL" properly.
- Invalid event type: Confirm the event type selected matches one supported by Reportei.
- Error responses from Reportei API: Check API key validity and network connectivity.
- Duplicate webhook registrations: The node attempts to manage webhook subscriptions but manual cleanup in Reportei may be necessary if issues arise.