Zapier automation context

Zapier supplies enterprise audit, agent activity, Zap history, and MCP context for AI-related automation workflows.

Release state

This guide documents the read-only zapier connector implemented in the platform connector surface. Zapier is one supported connector among many and is not required for Venturi to function.

Required access

The names below are Venturi manifest capabilities, not Zapier OAuth scopes:

Venturi capability	Purpose
Zapier.AuditLogs.Read	Read enterprise audit context.
Zapier.AgentActivity.Read	Read agent activity context.
Zapier.ZapHistory.Read	Read Zap execution history.
Zapier.MCP.Read	Read MCP or tool-call context where available.

Do not grant Zap edit, app connection mutation, or workspace administration scopes.

Use a Zapier Enterprise admin integration that can read the audit and workflow history made available by the customer’s plan. See Zapier’s Audit Log documentation. Agent and MCP context is collected only when that Enterprise workspace exposes it; the connector never submits the Venturi capability names above as scopes.

Setup

1. Create a dedicated Zapier enterprise integration for Venturi.
2. Grant only the read-only scopes above.
3. Store the credential reference in Venturi.
4. Set VENTURI_ZAPIER_LOOKBACK_DAYS if you need a poll window other than 30 days.
5. In Venturi, open Integrations and select Zapier and run Test connection.

Verification

• Audit, agent, Zap, or MCP rows appear for the expected workspaces.
• Zapier task counts are labeled as workflow context unless the plan exposes a native AI meter.
• Provider-account cost remains the cost truth when Zapier exposes context but no AI-specific meter.
• The read-only inventory test succeeds without Zap edit or connection-mutation access.

Rotation and offboarding

Rotate the Zapier integration credential through enterprise administration. Removing the connector stops new Zapier automation context syncs.