Zapier

Use Zapier as a no-code layer on top of UGC Automation - subscribe to UGC triggers, call UGC actions, and chain other SaaS steps in the same Zaps.

Prerequisites

• A UGC account with Automation entitled for your workspace
• Zapier account

Connect UGC

UGC Automation uses OAuth 2.0 with PKCE - see the canonical guide:

• [Automation OAuth (PKCE)](/api/automation/oauth) - register Zapier’s redirect URI, client_id, scopes, and token exchange.

Zapier’s OAuth UI will walk through browser login; you do not embed your UGSK_ API Key in Zap triggers.

What to build first

1. Trigger - pick a UGC event (campaign, slot, earnings, withdrawals, and more - full list on Automation triggers).

2. Action - create or fund a campaign, list slots, or fire other documented actions (Automation actions).

Payload signing for Automation delivery uses `X-UGC-Signature` (raw-body HMAC-SHA256) - verify it on every inbound delivery. See Automation overview.

Hub documentation

Step-by-step Zap examples, screenshots, and templates live with the broader integrations hub:

• Automation integrations overview
• Trigger reference
• Action reference