Automation
n8n
Open-source workflow automation tool with self-hosting support, code nodes for custom logic, and 400+ built-in integrations. Roiva syncs your n8n workflow execution counts — total, successful, and failed — as monthly metric observations for ROI measurement.
What gets synced
Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.
Workflow Executions
n8n.workflows.executions
Production executions that finished (one row per workflow, the workflow in the row's dimensions)
count
n8n.workflows.successful_executions
Successful production executions, on the first try or a retry (one row per workflow)
count
n8n.workflows.failed_executions
Failed production executions, error or crashed, even if a retry then succeeded (one row per workflow)
count
Common use cases
- Track how many times an AI automation workflow ran each month as a proxy for adoption and throughput
- Measure success and error rates for automated workflows before and after AI tooling changes
- Attribute automation volume growth to specific AI initiatives
- Use execution counts as the denominator in cost-per-run value formulas
How to connect
You connect n8n from inside Roiva, so you need a Roiva workspace first. Sign in to connect it now. New to Roiva? Take the free assessment and create your workspace at the end, or request an invite.
- In n8n: Go to Settings → n8n API, select Create an API key, give it a label and an expiration, and copy the key. The API isn't available on the n8n Cloud free trial
- Back in Roiva: Enter your n8n instance URL in the Instance URL field (e.g. https://n8n.yourcompany.com)
- Back in Roiva: Paste the API key and save the connection
- Back in Roiva: The connection page checks each step, including every workflow an initiative link names, and says what's missing. Once it's all ticked, click Test Connection
- Back in Roiva: Link this connection to an initiative on the Initiatives tab; optionally add a Filter with key workflow_ids and the IDs of the workflows to track, comma-separated
Tips for capturing value
- A workflow's ID is the part after /workflow/ in the n8n editor URL
- Without a workflow_ids filter, Roiva aggregates executions across all workflows — useful for account-wide automation volume tracking
- Roiva counts production executions much as n8n's Insights does, once they finish: runs started by a trigger, a webhook, the CLI or an error workflow, plus retries. Manual test runs, sub-workflow runs and evaluation runs don't count. A run that fails and is retried counts once as failed and once more for the retry, so successful plus failed is the total
- n8n only lists the executions it saves, so a workflow whose Save successful production executions setting is off shows no successful runs in Roiva
- Success rate (success_count ÷ count) is a useful signal for AI automation reliability initiatives
- Self-hosted n8n is ideal for organizations that cannot send data to third-party automation platforms
- n8n deletes old executions on a schedule set by your plan and settings (14 days or 10,000 executions by default when self-hosted). Roiva keeps each day's count once it has read it, so a later sync never lowers a month, but it can't count runs n8n deleted before Roiva first read them: a month n8n no longer holds in full when you connect is left out
Need help?
Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.
n8n
Start with the free AI ROI exposure assessment, then connect n8n once your workspace is set up.
Get your exposure report → Sign in to connectRelated integrations
