Automation
Zapier
No-code automation platform connecting thousands of apps through triggers and actions, enabling workflow automation without code. Roiva receives Zap run data via an inbound webhook — no API polling needed.
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.
Zap Runs
zapier.zaps.runs
Total Runs
count
zapier.zaps.successful_runs
Successful Runs
count
zapier.zaps.failed_runs
Failed Runs
count
Common use cases
- Count how many times an AI-powered Zap runs each month to measure automation volume
- Track error rates on automated workflows to identify reliability improvements
- Capture automation activity from tools that Roiva does not connect to directly
- Attribute Zap run counts to specific AI initiatives for ROI reporting
How to connect
You connect Zapier 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 Roiva: Create a Zapier connection — a unique ingest webhook URL is generated and shown once, so copy it then
- In Zapier: Webhooks by Zapier needs a paid Zapier plan (Professional, Team or Enterprise); it isn't available on the Free plan
- In Zapier: Open the Zap you want to track and add a final Webhooks by Zapier action step
- In Zapier: Choose the POST event and paste the connection's ingest URL into URL. Roiva keeps only a fingerprint of it, so if it's lost an admin replaces it from the connection page, and every Zap then needs the new one
- In Zapier: Set Payload Type to JSON and, optionally, add Data pairs run_id, zap_id, zap_name, status (success or error) and occurred_at (an ISO-8601 time such as 2026-09-14T15:30:00Z)
- In Zapier: Test the step, then Publish the Zap — Zapier only runs published Zaps
- In Roiva: Each time the Zap fires, a run is recorded and monthly metrics are updated in real time
- Back in Roiva: The connection page checks that the ingest URL is ready and says when runs start arriving
Tips for capturing value
- Add a Zapier filter step before the webhook action so only meaningful runs are counted
- Add an error handler to the step that can fail and, in its error path, post status=error to the same URL so failed runs are counted
- Send run_id (e.g. the trigger record's ID) so a replayed Zap run isn't counted twice
- A run counts in the month of its occurred_at, so a run posted late still lands in the month it happened
- Roiva refuses a run it can't read, such as a status other than success or error, or an occurred_at that isn't an ISO-8601 time. The step then fails, and the Zap's history shows why
Need help?
Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.
Zapier
Start with the free AI ROI exposure assessment, then connect Zapier once your workspace is set up.
Get your exposure report → Sign in to connectRelated integrations
