Automation

Make

Visual automation platform for building complex multi-step workflows with advanced data transformation and conditional logic. Roiva syncs your Make scenario runs and credit usage as monthly metric observations for ROI measurement.

← All integrations

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

Common use cases

Track how many times an AI automation scenario ran each month as a proxy for adoption
Measure success and error rates for automated scenarios before and after AI tooling changes
Attribute automation volume and Make credit usage to specific AI initiatives
Compare credits per run across scenarios to see which automations cost the most to run

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? 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 link 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)

Tips for capturing value

Scenario IDs are visible in the Make app URL when editing a scenario
Without a scenario_ids filter, Roiva aggregates executions across all team scenarios
Credits are what Make bills. Standard modules use 1 credit per operation, and Make's built-in AI features (AI Agents, AI Toolkit) add credits for tokens. With your own OpenAI or Anthropic key, token costs land on that provider's bill instead
Make keeps run history for 7 days on Free, 30 on Core, Pro and Teams, and 60 on Enterprise. Roiva fills in only the months that history covers in full, then keeps each day it has recorded after Make deletes it
Success rate (success_count ÷ count) is a useful signal for AI automation reliability
Make reserves most API endpoints for paid plans, so an organization on Make's Free plan may not be able to connect
A token works only in the zone it was created in. Make's Celonis-hosted zones aren't supported yet

Need help?

Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.

Make

Start with the free AI ROI exposure assessment, then connect Make once your workspace is set up.

Get your exposure report → Sign in to connect

Related integrations

Zapier

n8n