Zapier

Zapier connects to MonetizeIt with nothing MonetizeIt-specific: outbound is plain signed webhooks, inbound is the plain REST API. This page ties the two into a working Zap.

Trigger a Zap from MonetizeIt

This is the common direction — a licensing event kicks off a workflow (post to Slack when a trial is expiring, create a task when a customer nears their quota).

1. In Zapier, start a Zap with the Webhooks by Zapier trigger, event Catch Hook. Copy the custom webhook URL Zapier gives you.
2. In the portal, go to Settings → Webhooks → New subscription (or call POST /api/v1/webhooks/admin/subscriptions). Paste the Zapier URL, pick the event patterns you care about — for example Entitlement.* or MeteredUsage.OverageStatusChanged — and set a signing secret (32+ characters).
3. MonetizeIt immediately sends a one-time challenge to prove the endpoint is yours; the subscription goes Active once it answers. Zapier’s Catch Hook answers automatically, so the subscription activates as soon as you finish the trigger step.
4. Use Test on the subscription (or .../test-fire) to push a sample event so Zapier can capture the shape and you can map fields.

Each delivery is signed. If your Zap forwards the payload somewhere that needs to trust it, verify the webhook-signature header as shown in Receiving webhooks. Deliveries are at-least-once, so deduplicate on the webhook-id header if the downstream action isn’t idempotent.

Manage subscriptions programmatically

If you are building a Zapier app or a partner integration rather than a one-off Zap, you can let the integration create and manage its own webhook subscriptions instead of doing it by hand in the portal.

1. In Settings → Integrations, create a set of integration credentials. You get a client ID (integration.…), a one-time secret, the token URL (https://<your-subdomain>/auth/connect/token) and the scope webhooks.integrator.
2. Exchange them for a token with the OAuth client_credentials grant (see Authentication).
3. Call the integrator endpoints under /api/v1/webhooks/integrator/… to list, create, verify and rotate subscriptions. The integration only ever sees its own subscriptions, and the tenant is fixed by the token — no tenant header to set or spoof.

Managing subscriptions this way requires your plan to include integrations.

Let a Zap call back into MonetizeIt

To have a Zap do something in MonetizeIt — create an entitlement from a Stripe event, pause one on a support signal — a Webhooks by Zapier action makes the REST call. There are two ways to authorize it:

• Reacting to a delivery — if the subscription requested callback scopes, every delivery carries a short-lived token in the webhook-callback-token header. Forward it as the Authorization: Bearer … on your callback. It is already scoped to exactly what you allowed, expires in minutes, and needs no stored secret. Callback tokens grant read/create/update verbs only — never delete or wildcards.
• Standalone actions — for a Zap that isn’t reacting to a MonetizeIt delivery, authenticate with admin or operational client credentials (Authentication) and call the API directly.

The Stripe page is a full worked example of this callback direction — a billing event in, an entitlement change out.