Zapier

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

• 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

1. In Roiva: Create a Zapier connection — a unique ingest webhook URL is generated automatically
2. In Zapier: Open the Zap you want to track and add a final Webhooks by Zapier action step
3. In Zapier: Set the action to POST and paste the connection's ingest URL, which the connection page shows admins with a Copy button
4. In Zapier: Optionally include a JSON body with run_id, zap_id, zap_name, status, and occurred_at
5. In Roiva: Each time the Zap fires, a run is recorded and monthly metrics are updated in real time
6. Back in Roiva: The connection page checks that the ingest URL is ready and says when runs start arriving

• Add a Zapier filter step before the webhook action so only meaningful runs are counted
• Pass status=error in the body from Zapier's error handler path to track failure rates
• Use run_id (e.g. the trigger record ID) to make webhooks idempotent against Zapier retries