Zapier Integration Hub

Zapier is the lightweight glue layer in the OpenClaw automation stack — primarily used as an inbound trigger source for HubSpot zaps and multi-app workflows connecting 6,000+ apps without custom code. Read this hub when diagnosing a Zap that isn’t firing, when wiring a new HubSpot event into a downstream action, or when an agent needs to trigger automation via the AI Actions API. KB last verified 2026-03-04.

Quick reference

Field	Value
Vendor	Zapier
URL	https://zapier.com
KB doc	API
Auth method	OAuth 2.0 (Workflow API) / API Key (AI Actions) / no-auth URL (Catch Hook)
Auth credential	op://Aurora/zapier/api-key
Cred-proxy port	n/a (until NemoClaw B1-B6 ratified — see nemoclaw-audit-2026-05-03)
Webhook port	n/a (Zapier is inbound trigger source; VPS posts OUT to Zapier Catch Hook URLs)
Webhook handler	n/a (no inbound VPS handler for Zapier)
Webhook dedup table	processed_webhook_events (24h TTL) — apply if Zapier ever posts inbound
Tunnel path	n/a
Outbound API base	https://api.zapier.com/v1 (Workflow API); https://hooks.zapier.com/hooks/catch/{id}/{key}/ (Catch Hook); https://actions.zapier.com/api/v1 (AI Actions)
Rate limits	100 req/min (free); 1,000 req/min (Team). Tasks/month capped by plan: Free 100, Starter 750, Professional 2,000, Team 50,000
Rate-limit action	429 → exponential backoff (3 retries), Discord ops alert
Cost	Free → $19.99/mo(Starter)\to$49/mo (Professional) → $69/mo (Team); annual discount ~33%
Backup/recovery	Vendor-owned. Zap history retained 90 days (Free) / 1 year (Professional+)
Discord alert channel	ops
Drift cadence	On API change / manual
Status	production

Components

• workspace/knowledge-base/zapier/API.md — Full Workflow API, Catch Hook, AI Actions, Zap run history endpoints; last_verified 2026-03-04
• workspace/knowledge-base/zapier/_audit/ — Audit trail for KB drift checks
• workspace/knowledge-base/zapier/examples/ — RERI Zap pattern examples (HubSpot deal → Discord, lead form → CRM, DocuSign signed → archive)
• [[wiki/_hubs/integrations/hubspot]] — Zapier’s primary trigger source in RERI workflows
• [[wiki/_hubs/integrations/discord]] — Most common Zapier action destination (#better-acquisitions, deals)
• [[wiki/_hubs/integrations/1password]] — Credential store for Zapier OAuth tokens and AI Actions keys

How it’s used

• Trigger condition: HubSpot deal stage changes to “Under Contract” or “Closed Won” → Zapier Catch Hook → downstream notifications (Discord) + record creation (Google Sheets, Glide)
• Workflow: OpenClaw agent POSTs JSON to Zapier Catch Hook URL (stored in master.env). No inbound handler needed on the VPS — Zapier originates the action.
• Agents involved: Acquisitions agents fire lead zaps; BetterFiles TC agents fire DocuSign completion zaps. No direct Zapier SDK — plain HTTP POST via fetch().
• Failure mode: Zap errored — Zapier retries 4× (schedule: 15 min → 1 hr → 4 hr → 16 hr). After all retries: Zap marked “errored” in history. Check Zap run history at zapier.com/app/history. If task limit reached, Zaps queue silently — watch Billing → Task Usage.
• Success criteria: {"status": "success"} response on POST to Catch Hook URL; Zap run history shows “success” within 2 seconds of trigger.

Cross-links

Agents that touch this

• _summary — fires lead creation zaps on new IL/PropStream deals
• _summary — fires DocuSign-complete zaps after TC package signed

Skills that invoke this

• acquisitions-outreach — Stage 1 outreach may trigger HubSpot zap for CRM entry
• hubspot-deal-ingest — Deal creation can route through Zapier for multi-system fan-out

Plans that govern this

• openclaw-fragmentation-fix-2026-05-01 — automation platform rationalization (Zapier vs Make vs n8n decision deferred)
• nemoclaw-audit-2026-05-03 — cred-proxy pattern (B1 pending) would gate Zapier OAuth tokens through credential proxy

Feedback rules

• feedback_no_plaintext_creds — Zapier Catch Hook URLs contain no secrets by default; use Filter step for shared secret validation
• feedback_action_gate_violation_repeated — confirm before firing any live Zap in code context
• feedback_blocker_surfacing — if Zap task limit is reached, surface as blocker; do not silently drop events

KB / source docs

• API — Workflow API, Catch Hook, AI Actions, Zap run history, RERI patterns
• examples — Active Zap patterns for RERI (deal alerts, lead response, DocuSign archive)

System maps

• external-integrations — Zapier’s position in RERI’s integration graph
• deal-lifecycle-map — Where Zapier fires in the deal flow

Related: Automation platforms cluster

Zapier, Make, and n8n form the RERI automation platform cluster. Make (make) is the cluster anchor — it has webhook handlers on both inbound and outbound and is the richer automation orchestrator. Zapier is used for HubSpot-native trigger flows. n8n (n8n) is staging as an OSIL self-improvement pipeline candidate. Decision on rationalization pending — see openclaw-fragmentation-fix-2026-05-01.

Related: Credential layer cluster

All Zapier credentials (OAuth tokens, AI Actions API key, Catch Hook URLs with embedded secrets) are stored in 1Password vault Aurora. Hub: 1password. Per feedback_no_plaintext_creds and G-NO-PLAINTEXT-CREDS — no plaintext secrets in any tracked file. Reference as op://Aurora/zapier/<field> only.

Open issues / TODOs

• Confirm current Zapier plan tier and monthly task usage (check Billing → Task Usage at zapier.com)
• Inventory all active Zaps and add to WORKFLOW-PATTERNS.md if recurring ≥3×
• Add Zap dedup filter step to any Catch Hook Zap that could double-fire on HubSpot stage polling
• Decision pending: rationalize Zapier vs Make vs n8n automation footprint (see openclaw-fragmentation-fix-2026-05-01)

Recent activity

• 2026-05-04: Hub created (Wave 3 W3-S6). KB last_verified 2026-03-04.