Automation
Make
Roiva counts the runs your AI scenarios complete in Make and the credits each uses, and prices the manual work they replace at your ops rate.
What it answers
How much manual work an AI scenario replaces, and what its credits cost to get there
What Roiva reads
Your team's scenarios and their run logs from the last 60 days. Roiva keeps run counts and credits per scenario, by name.
Setup
An API token with scenarios read, and your team ID and zone
What you can measure with Make
Manual work, priced
Successful runs each month × the minutes of manual work one run replaces × your ops hourly rate, as freed capacity. Roiva starts from five minutes a run, counted as an estimate, until you time the task or record your own figure.
make.scenarios.successful_executions
Starts from the Workflow Automation with n8n, Make or Zapier template
Credits per scenario
Credits used by each scenario, month by month, so one that saves little and burns credits shows beside the ones worth running.
make.scenarios.credits
Errors, tracked beside it
Failed runs aren't counted as work done, and their rate shows a scenario that started breaking.
make.scenarios.failed_executions
Only whole months
Make keeps run logs for a limited time by plan, so Roiva records only the months it still holds whole, rather than a month cut short.
A worked month
An AI invoice-reading scenario
Manual Work Replaced by Automated Workflows, from the Workflow Automation with n8n, Make or Zapier template, for September
| Successful runs in September | 2,640 | Make |
| Minutes of manual work one run replaces | 4 | Your time study |
| Ops hourly rate | $45 | Roiva's default, until you set yours |
2,640 runs × 4 minutes × $45 ÷ 60
$7,920 freed capacity for September, reported beside cash ROI, never in it
Make's change-log entries sit beside the runs in its logs and aren't counted. The credits are the initiative's cost once your Make bill is booked to it.
Illustrative figures. Roiva keeps every input with the entry it calculates, and none of it counts until it's approved.
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.
Scenario Executions
make.scenarios.executions
Total runs (one row per scenario, the scenario in the row's dimensions)
count
make.scenarios.successful_executions
Successful runs (one row per scenario)
count
make.scenarios.failed_executions
Failed runs (one row per scenario)
count
make.scenarios.credits
Make credits used (one row per scenario)
count
What Roiva keeps
Reads: Your team's scenarios and their run logs from the last 60 days. Roiva keeps run counts and credits per scenario, by name.
Keeps: Totals only, such as a month's count or spend. No record is kept.
How to connect
You connect Make from inside Roiva, so you need a Roiva workspace first. Sign in to connect it now. New to Roiva? Start free with your work email, take the free assessment and create your workspace at the end, or request an invite.
- In Make: Click your avatar (bottom left) → Profile → API tab → Add token, and tick scenarios:read under Scopes. Copy the token right away; Make hides it once you leave the page
- In Make: Click Team in the left sidebar. The team dashboard's URL holds both values Roiva needs: in us1.make.com/134/team/dashboard, us1 is your zone and 134 is your Team ID
- Back in Roiva: Enter your API key, Team ID, and zone (us1, us2, eu1 or eu2) and save the connection
- Back in Roiva: The connection page checks each step, including every scenario an initiative names, and says what's missing. Once it's all ticked, click Test Connection
- Back in Roiva: Link this connection to an initiative; optionally add a Filter with key scenario_ids and the IDs of scenarios to track (comma-separated)
Need help?
Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.
Make
Start free, then connect Make once your workspace is set up. Or begin with the free AI ROI exposure assessment.
Start free → Sign in to connectRelated integrations