Integrations

Plays nicely with what
you already use.

Pulsily is built to live alongside the tools a healthy church staff team already runs — Planning Center, Slack, email, mobile. Not a replacement. The pastoral-care layer on top.

Planning Center People

Live

Your system of record. Our roster.

Two-way sync for people, teams, and memberships. PCO stays the source of truth — add a new leader there and Pulsily picks them up within minutes. Disconnect anytime; we don't hold your data hostage.

  • Two-way person + team + membership sync
  • OAuth connection, no API key juggling
  • Initial backfill, then live delta sync
  • Disconnect and re-connect freely

Slack

Live

Urgent answers route where your staff already lives.

When a check-in response trips an urgent flag — someone asked for prayer, named a crisis, or scored a 1 on the rhythm question — Pulsily can post a quiet alert to a Slack channel of your choice. No notifications for green check-ins, only the ones that need eyes.

  • Per-channel routing (e.g., #care-team)
  • Mention specific staff for specific signals
  • Always-on opt-in — never the default
  • Plain-text, minimal-formatting messages

Email under your domain

Live

Pulsily disappears, your church voice doesn't.

Every email Pulsily sends — the monthly check-in invitation, the leader digest, the reminder for an overdue response — goes out from your domain. Volunteers see a message from their pastor, not from a SaaS bot. We don't add 'powered by' anywhere.

  • Amazon SES delivery (yours, configured)
  • SPF + DKIM friendly
  • Your church name + reply-to in every send
  • Plain-prose templates, not marketing-style

iOS app

Live

A native mobile experience for volunteers — optional.

Volunteers can respond to check-ins on the web (one-click link in the email, no login required). For churches that want a more app-like experience, there's an iOS app where volunteers can see their answer history, log a touch with a leader they care about, and review pinned notes.

  • Native iOS via Expo / React Native
  • Optional — web works fully without it
  • Push notifications for new check-ins
  • Volunteer-side only; staff use the web admin

Stripe

Live

Self-serve billing with a real billing portal.

Pulsily uses Stripe for plan upgrades and the billing portal. Update your card, change your plan, download invoices, cancel — all in a UI Stripe built and we didn't have to reinvent. We never see your card details.

  • Stripe Checkout for upgrades
  • Stripe Billing Portal for self-serve changes
  • Monthly + annual billing (annual saves ~17%)
  • Real invoices with your church name

CSV import / export

Live

When you'd rather not connect anything.

Not every church uses Planning Center. Pulsily can ingest your roster from a CSV in under a minute and export responses + touch logs back out the same way. Run it as a stand-alone if you'd rather.

  • Import people + teams + memberships
  • Export check-in responses
  • Export touch logs + notes
  • Standard CSV — works with any spreadsheet

Outbound webhooks

Multi tier

For the church that runs a custom dashboard.

Send urgent-flag events and check-in completions to any webhook URL — a custom Slack-compatible endpoint, a Make.com flow, a denominational rollup, your staff intranet. Available on Multi today, on request.

  • Slack-compatible payload format
  • Per-event subscriptions
  • HMAC signing for verification
  • Multi tier — write us to enable

Need something we don’t have?

We’re small enough that real conversations move the roadmap. If there’s an integration your staff team needs, tell us — we’ll either ship it or help you route around it.