Zapier & Make Integration

Charon Gate works as a reliability layer in front of any HTTP destination — including Zapier Webhooks and Make (Integromat) webhook triggers. This means you get durable capture, automatic retries, and DLQ alerting for your no-code automations.

How it works

Normally, providers (Stripe, GitHub, etc.) send webhooks directly to Zapier or Make. If your Zap or scenario is inactive, at quota, or temporarily unavailable, events are lost silently.

With Charon Gate in front:

Provider → POST /ingest/{id} (Charon Gate) → Zapier or Make webhook URL

Charon Gate captures the event, verifies the signature, and forwards it to your Zapier or Make webhook URL. If the forward fails (Zapier is down or at limit), Charon Gate retries automatically. If all retries fail, the event enters the DLQ and you get an alert.

Setting up with Zapier

1. Create a Zapier Webhook trigger

1. Create a new Zap
2. Choose Webhooks by Zapier → Catch Hook
3. Copy the provided webhook URL (looks like https://hooks.zapier.com/hooks/catch/…)

2. Create a Charon Gate endpoint

1. Go to Endpoints → New endpoint
2. Select your provider template (Stripe, GitHub, etc.)
3. Set Destination URL to your Zapier webhook URL
4. Save — copy the Ingest URL

3. Point your provider at Charon Gate

Update your provider (Stripe, GitHub, etc.) to send webhooks to the Charon Gate ingest URL instead of the Zapier URL directly.

Now every event goes through Charon Gate first — with retries, DLQ, and alerting — before arriving at your Zap.

Setting up with Make (Integromat)

1. Create a Make Webhook

1. Create a new scenario
2. Add a Webhooks → Custom webhook module
3. Click Add to create a new webhook → copy the URL

2. Create a Charon Gate endpoint

Same as Zapier: create an endpoint in Charon Gate with your Make webhook URL as the destination.

3. Update your provider

Point your provider's webhook configuration to the Charon Gate ingest URL.

Tips for no-code workflows

Replay on Zap deactivation

Zaps automatically deactivate after too many errors. If this happens during a busy period, you may have a backlog of events in the Charon Gate DLQ. Once you fix the Zap and reactivate it, use the Batch replay feature in Charon Gate to replay the backlog.

Digest mode for high-volume sources

If your provider sends many events per minute, consider enabling Digest mode on your Charon Gate alert rules. This batches DLQ notifications into a single summary rather than sending an alert per event.

Use the test delivery button

Charon Gate's Test delivery button sends a synthetic event to your Make or Zapier webhook URL. Use this to verify your scenario or Zap handles the payload shape correctly before going live.

Supported providers

Charon Gate's provider templates handle signature verification automatically for:

• Stripe (Stripe-Signature / HMAC-SHA256)
• GitHub (X-Hub-Signature-256 / HMAC-SHA256)
• Shopify (X-Shopify-Hmac-SHA256)
• Clerk (Svix HMAC)
• Resend (Svix HMAC)
• Generic (bring your own HMAC secret)

For providers not listed, use the Generic template and configure the secret manually.