Skip to content

Zapier automation context

Zapier supplies asset-change, Zap execution, and MCP server context for AI-related automation workflows.

Onboarding scope

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

Plan prerequisite

This connector requires the Zapier Enterprise plan, because Zapier offers Log Streams only on Enterprise. Only a Zapier super admin or owner can create a Log Stream. See Zapier’s Log Streams article.

Required access

The names below are Venturi capability identifiers, not Zapier OAuth scopes:

Venturi capability Purpose
Zapier.AuditLogs.Read Receive asset-management events: the account activity that the Zapier audit log also records.
Zapier.AgentActivity.Read Agents activity context. Zapier offers no API or Log Stream event for it, so this capability returns no rows.
Zapier.ZapHistory.Read Receive Zap execution events.
Zapier.MCP.Read Receive MCP server and tool events.

The vendor-side authorization is a Zapier Log Stream, not an API credential. Zapier sends each selected event to an HTTPS endpoint as a signed POST request, so Venturi never holds a Zapier sign-in, API key, or permission to change Zaps, connections, or account settings.

  • Destination. Venturi provides a tenant-specific HTTPS destination URL on the Zapier connector page in Integrations / Zapier.
  • Signing secret. Zapier signs each request with HMAC-SHA256 using the Log Stream secret, which must be at least 16 characters, and sends the signature in the X-Zapier-Signature header with the signing time in X-Zapier-Timestamp. Venturi verifies both and rejects unsigned or mismatched requests. The secret is the only Zapier credential Venturi stores.
  • Asset-management events. Changes to app connections, variables, MCP servers, tables, account membership and groups, API credentials, folders, and Zaps, each with the actor, the affected object, and the time.
  • Zap execution events. zap_execution.success, zap_execution.error, and zap_execution.halted, each with the Zap ID, run ID, start time, and Zap owner.

Zapier offers no API for its audit log, so the connector does not read the audit log page itself; it receives the same account activity as asset-management events. The audit log also lists Zapier Agents activity, which Zapier does not send through Log Streams. MCP context covers MCP server and tool changes (mcp_server.* events); Zapier does not stream individual MCP tool calls. A Log Stream carries only events that occur after it is created, so create it on the day you connect Zapier.

Setup

  1. Copy the HTTPS destination URL from Integrations / Zapier.
  2. In Zapier, have a super admin or owner open the Admin Center, select Log streams under Insights, and select Create log stream. Paste the Venturi URL as the Destination URL and select Generate to create the Secret.
  3. Select all asset-management and execution log events, then select Save.
  4. Store the Log Stream secret as an encrypted credential reference in Settings / Admin / Credentials.
  5. The default lookback is 30 days; set VENTURI_ZAPIER_LOOKBACK_DAYS to change it. The first sync can include only events received since you created the Log Stream. See sync windows and failure behavior.
  6. In Integrations / Zapier, run Test connection.

Verification

  • Test connection passes the read-only boundary check: signed Log Stream requests verify against the stored secret, and Venturi holds no Zapier API credential that could edit Zaps or connections.
  • The Log Stream shows as active in the Zapier Admin Center, and its event count grows as Zaps run.
  • Asset, Zap execution, and MCP server rows appear for the expected Zapier account.
  • 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.

Rotation and offboarding

To rotate, edit the Log Stream in the Zapier Admin Center, generate a new secret, and update the credential reference in Settings / Admin / Credentials. To offboard, pause or delete the Log Stream in Zapier and remove the connector. Removing the connector stops new Zapier automation context syncs.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Zapier automation context
Page: https://docs.venturi.systems/connectors/zapier/