How Zapier integrations work
This page explains what the Zapier integration does, how the connection is made, what triggers and actions are available, and when to use Zapier versus the direct REST API.
The short version
Section titled “The short version”Connecting Zapier lets you automate tasks between MapleGather and thousands of other apps without writing code. You authenticate once through a web-based consent flow, and then configure individual automations (“Zaps”) inside Zapier’s own interface.
How it works
Section titled “How it works”Zapier is an automation platform that connects apps using a trigger-action model: something happens in one app (the trigger) and Zapier automatically does something in another (the action). You configure this in Zapier’s browser interface; MapleGather provides the triggers and actions, and Zapier handles the routing.
Triggers and actions available at M1:
- Trigger: New payment received — fires within about five minutes of a payment succeeding. The trigger rides MapleGather’s webhook transport, so it shares the same reliability and retry guarantees as the webhook system.
- Action: Create a contact — lets a Zap create a member record in your MapleGather org (for example, from a Mailchimp form submission). If the submitted email already belongs to an existing member, the action returns that member’s record rather than creating a duplicate. This deduplication is guaranteed by MapleGather’s idempotency and dedup logic.
How the connection is made: when you select Open in Zapier from the Connect Zapier page in MapleGather, a key is minted for the connection and an OAuth consent flow completes on MapleGather’s auth layer (Keycloak). MapleGather has no UI step for the OAuth handshake itself — you complete it in Zapier’s browser. Once the consent completes, the connection appears in your MapleGather Integrations page as active.
You do not need to select API scopes or configure an HMAC secret for the Zapier connection. The connection uses a pre-scoped key, and the OAuth handshake handles authorization transparently — the one-click no-code path.
Sandbox mode: when your MapleGather organization is in sandbox mode, the payment trigger fires on the sandbox event stream only. Production events do not leak into sandbox Zaps, and sandbox events do not fire in production Zaps.
Why it works this way
Section titled “Why it works this way”Zapier is the right choice when you want to connect MapleGather to another app (email, spreadsheets, CRM) without writing code or maintaining infrastructure. The direct REST API is the right choice when you need custom logic, real-time response, higher throughput, or fine-grained control over error handling.
The no-code path is designed so the Volunteer Admin never sees a scope catalog or an HMAC secret — those are developer surfaces. The connection surface shows only “the key Zapier will use” and the available trigger/action list.
Edge cases & boundaries
Section titled “Edge cases & boundaries”- You can connect multiple Zapier accounts to the same MapleGather organization. Each connection is an independent record managed separately.
- Zapier polls for triggers approximately every five minutes on most plans. If near-real-time delivery is important, consider the webhook endpoint approach — your receiver gets the event within seconds of it occurring.
- If a Zap action posts a malformed contact, MapleGather returns an RFC 7807
ValidationProblemresponse that Zapier surfaces in its own run log. MapleGather does not create a partial member record in that case. - If the OAuth consent is abandoned mid-handshake (for example, the admin closes the Zapier tab), no
Integrationpersists; the on-ramp stays open for a fresh attempt.