Reportei Trigger icon

Reportei Trigger

Handle Reportei events via webhooks
Join our community

Overview

This node acts as a webhook trigger for Reportei events, allowing users to subscribe to various event types from their Reportei projects. When an event occurs in Reportei (such as report creation or dashboard creation), the node receives the event data via a webhook and triggers the connected workflow in n8n.

Common scenarios include:

  • Automating follow-up actions when a new report is created or viewed.
  • Tracking milestones or goals within Reportei projects.
  • Integrating Reportei event data with other systems like CRMs, messaging platforms, or databases.

For example, you could use this node to automatically send a notification to a Slack channel whenever a new dashboard is created in Reportei, or to update a CRM record when a control goal is met.

Properties

Name Meaning
Project Name or ID Select the Reportei project to which you want to add the trigger. You can choose from a list of available projects or specify a project ID using an expression.
Event Type The specific Reportei event to subscribe to. Options include: Automation Executed, Control Goal Met, Control Goal Not Met, Dashboard Created, Report Created, Report Viewed, Timeline Milestone Added.
Custom Webhook Base URL Optional. If you are behind a tunnel or need to specify a public domain, provide your custom base URL here. This replaces the default localhost address in the webhook URL to ensure proper reception of events.

Output

The node outputs the webhook payload received from Reportei in the json field of the output data. The structure corresponds directly to the event data sent by Reportei and varies depending on the event type subscribed to.

No binary data output is produced by this node.

Example output JSON structure (simplified):

{
  "event_type": "report_created",
  "client_id": "12345",
  "source": "n8n",
  "url": "https://your-domain.com/webhook",
  "data": {
    // event-specific details here
  }
}

Dependencies

  • Requires an API key credential for authenticating with the Reportei API.
  • Needs network accessibility for receiving incoming webhook POST requests from Reportei.
  • Optionally requires a publicly accessible URL or tunnel if running n8n locally, specified via the "Custom Webhook Base URL" property.

Troubleshooting

  • Webhook not triggering: Ensure that the webhook URL is publicly accessible by Reportei. If running locally, use a tunneling service or set the "Custom Webhook Base URL" correctly.
  • Subscription errors: Verify that the provided project ID and event type are valid and that the API key has sufficient permissions.
  • Duplicate or missing events: Check that only one active webhook subscription exists per event/project combination to avoid duplicates or missed events.
  • Common error messages:
    • Authentication failures: Confirm the API key credential is correct and active.
    • HTTP request failures: Check network connectivity and firewall settings.

To resolve these issues, verify credentials, webhook URLs, and network configurations.

Links and References

Discussion