Zapier
Hand off Moonborn webhook events to Zapier's 6,000+ app catalog. Drift alerts to PagerDuty, marketplace publications to a Notion log, etc.
Zapier is the breadth lever — when your team's stack lives outside the explicit Moonborn integration list (Slack, Discord, generic webhooks), Zapier connects to it. Marketing teams running on Notion + HubSpot, ops teams on PagerDuty + Linear, content teams on Airtable — all reachable via Zapier zaps triggered by Moonborn webhooks.
Setup
- In Zapier, create a Zap with "Webhooks by Zapier" as the trigger. Pick the "Catch Hook" trigger; Zapier gives you a URL.
- Subscribe a Moonborn webhook to that URL:
const hook = await client.webhooks.createWebhook({
url: 'https://hooks.zapier.com/hooks/catch/123.../X...',
events: ['persona.audit_failed', 'marketplace.persona.published'],
description: 'Zapier — multi-app distribution',
});- In Zapier, parse the payload and route to your downstream app: create a Notion row, send a PagerDuty incident, append to Airtable, etc.
The payload is Moonborn's standard JSON envelope (id, type, occurredAt, data). Zapier's "Parse" step makes the fields available to subsequent actions.
Pattern: route by event type
In Zapier, use a "Filter" or "Paths" step on event.type:
persona.audit_failed→ PagerDuty + Slackmarketplace.persona.published→ Notion log + Twitter postsubscription.upgraded→ CRM update + welcome email
One Moonborn webhook → many Zapier-driven actions.
Cost note
Each event costs one Zapier task. High-volume orgs running tens of
thousands of persona.created events per day will burn Zapier task
quota fast. For high-volume routing, subscribe directly via your own
worker or hit the Moonborn-native Webhooks
surface instead.
Honest scope
Zapier is fan-out from Moonborn, not into. Moonborn doesn't have a Zapier trigger app today — you can't "when something happens in Zapier, do X in Moonborn." That's a future direction; for now, every flow is Moonborn → Zapier → other.
Tier
Any tier (webhooks are Team+, so effectively Team and up).
Next
- Webhooks integration.
- Brand-side patterns: Brand voice variants use case.