Skip to Content

Zapier

Zapier connects Ministrium with 6,000+ apps without coding. Handy for:

  • Create an Asana task when there’s a new prospect.
  • Notify Slack when a donation exceeds $1,000.
  • Add to Google Sheets every new visitor.
  • Hail a Lyft when a member requests prayer for a hospitalization.
  • Create a Google Calendar event when a service plan is scheduled.

Available triggers

Ministrium events that can start a Zap:

TriggerWhen it fires
New MemberA member is created
Member UpdatedA member is updated
New ProspectA prospect is created (Connect Card)
Prospect ConvertedProspect becomes member
New DonationDonation completed
Recurring Donation CreatedNew recurring gift
Recurring Donation FailedRecurring charge failed
Attendance RecordedCheck-in recorded
Event CreatedNew event
Event RegistrationSomeone registers for an event
Group CreatedNew cell group
Group MultipliedGroup multiplication
Prayer RequestNew prayer request

Available actions

What a Zap can do in Ministrium:

ActionDoes
Create ProspectCapture a prospect from another form
Update MemberEdit fields of a member
Add TagTag a member
Record AttendanceMark attendance
Create Donation (manual)Record an off-Stripe donation (e.g. check)
Send NotificationTrigger transactional push/email

Connect

  1. In Zapier, search “Ministrium”.
  2. Connect → OAuth with your Ministrium account.
  3. Grant permissions to the right tenant.
  4. The Zapier token is scoped to the tenant and the role of the connecting user.
Connecting user's permissions

The Zap acts with the connecting user’s permissions. Connect as org_admin and the Zap can do everything. Connect as care_pastor and only what that role allows. We recommend a dedicated service user.

Examples

Slack: large-donation alert

Trigger: New Donation in Ministrium Filter: amount > 1000 Action: Send Channel Message in Slack Channel: #finance Message: "🎉 {{donor.name}} gave {{amount}} to {{fund.name}}"

Google Sheets: visitor log

Trigger: New Prospect in Ministrium Action: Create Spreadsheet Row in Google Sheets Spreadsheet: "Visitors 2026" First Name: {{first_name}} Last Name: {{last_name}} Phone: {{phone}} Came From: {{source_channel}}

Asana: follow-up task

Trigger: New Prospect in Ministrium Action: Create Task in Asana Project: "Pastoral pipeline" Title: "Call {{first_name}} {{last_name}}" Due: in 2 days Assignee: care-team

Rate limits

Zapier respects API rate limits:

  • Starter plan: 60 req/min — Zaps that spike can be throttled.
  • Growth plan: 600 req/min — fits churches < 5,000 members.
  • Business+ plan: 6,000 req/min — no issue.

If a Zap fails on rate limit, Zapier auto-retries with backoff.

Best practices

  1. Early filters: filter in the trigger, not in later steps, so you don’t burn Zapier tasks needlessly.
  2. Idempotency: if the Zap creates resources in Ministrium, use external_id to avoid duplicates.
  3. Direct webhook for low latency: Zapier has 1-15 min latency. For real-time use direct Webhooks.
  4. Test with real data: Zapier lets you test with a historical event before activating.

Alternative: pure webhooks

If Zapier is too expensive or too slow, subscribe directly to Webhooks and process in your backend. More control, requires development.

Last updated on