UGCDocumentation

Automation Overview

Connect the platform to Zapier, Make & n8n without code

Updated September 18, 2026

Automate campaign creation, funding, and slot monitoring without writing code.

Technical references: · · ·

What you can automate

Triggers - get notified on campaign lifecycle (campaign_funded, campaign_completed, ...), slot lifecycle (slot_submitted, slot_approved, ...), creator earnings (earnings_credited, earnings_released), wallet cash-out (withdrawal_*), AI/storage events, and checkout/subscription/username events. See the (31 names; Console picker: 19 UGC events).

Actions - list/create/fund campaigns, list a campaign's slots, check username availability, and generate crypto deposit addresses. See the .

How to connect

Option 1: OAuth ("Connect")

Recommended for most users.

1. Open your automation platform (Zapier, Make, or n8n).

2. Search for this platform's app.

3. Click "Connect" and authorize in your browser.

4. Build your automation.

Uses OAuth 2.0 with PKCE (S256); no client secret required for public clients.

Option 2: API key

For advanced users and server-side scripts.

1. Sign in and open Integrations in your dashboard.

2. Under API key connections, click Generate API key.

3. Copy your key (UGAU_live_... or UGAU_test_...).

4. Use it as a Bearer token in your automation platform or custom scripts.

Automation connection keys (UGAU_...) are separate from your self-serve developer API Key (UGSK_) - use the automation key for Zapier/Make/n8n and REST-hook subscriptions specifically.

Webhook delivery security

Every trigger delivery carries:

code
X-UGC-Signature: <hex hmac-sha256 of the raw JSON body>
X-UGC-Event-Id: <event id, for idempotent processing>

Verify by recomputing HMAC-SHA256 of the raw request body using the hookSecret returned when you subscribed, then comparing with a timing-safe equality check. Reject unsigned or mismatched deliveries.

Idempotency & rate limits

POST/mutating actions accept an Idempotency-Key header (24h TTL) so retries never duplicate a campaign, fund, or deposit-address call. Automation endpoints follow the platform's standard per-key rate limits; a 429 response means back off and retry with exponential backoff.

Availability

Automation is gated behind feature flags on your account. If /automation/* returns a disabled-feature error, contact support to enable it.

Did this solve your problem?