Integration Products | Campaign Creators

MinistryPlatform HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:41:40 AM
Integration Assessment
Integration Assessment · Faith & Nonprofit

MinistryPlatform × HubSpot

How a church that runs people, groups, events and giving in MinistryPlatform can bring households, participation and next steps into HubSpot, so guests are followed up, members are invited to the right next step, and pastoral care stays where church leadership keeps it.

MinistryPlatform REST APIOAuth 2.0 client credentialsTable webhooksHouseholds and participantsJourneys and milestonesCare data stays in MP
Platform ownerACS Technologies
Integration typeCustom build on the MinistryPlatform REST API
Primary directionMP → HubSpot, guest forms and opt-outs back
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does MinistryPlatform integrate with HubSpot?

MinistryPlatform is where a church keeps its people, households, groups, events, attendance, serving and giving. HubSpot is where it can run guest follow-up, next-steps journeys and church-wide communication. Connecting the two means a first-time guest gets a timely welcome, a regular attender is invited to the right group or serving team, and staff see one picture of each person's involvement.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The REST API is documented in each church's Swagger page. A church administrator creates the API client.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

MinistryPlatform exposes its tables through a documented REST API with OAuth 2.0 and table-level webhooks, so HubSpot can run guest-to-member journeys on live participation data while care and giving detail stay in MinistryPlatform.

Campaign Creators assessment

We found no HubSpot-built or ACS Technologies-built HubSpot app for MinistryPlatform, so this is a direct build on the MinistryPlatform REST API. CC's build reads contacts, households, participant type and status, campus, group and serving roles, event attendance and milestones into HubSpot. HubSpot guest forms and email opt-outs write back. Care cases, prayer requests and notes never leave MinistryPlatform, and giving reaches HubSpot only as summaries if church leadership approves.

Scorecard
API accessChurch-issued API client
Public docsGood, some gaps
Call budgetNot published
Build complexityModerate

Ratings are CC judgments from ACS Technologies' public MinistryPlatform help and developer documentation. Rate limits and table names are confirmed against the church's MinistryPlatform instance during discovery.

Strength

Table-level API and webhooks

The REST API reads and writes any table the API client can see, with $Filter, $Select, $Top and $Skip. Webhooks fire on create, update or delete for a chosen table, limited to the fields and conditions the church sets.

Plan for

Pastoral care and giving privacy

Care cases, household care logs, prayer requests and notes stay in MinistryPlatform. Giving appears in HubSpot only as summary figures, and only if church leadership approves it.

Gate

API client permissions

An API client inherits the security roles of its Client User. The church creates a dedicated user that can read only the approved tables, which is how the field allowlist is enforced.

02 — API modules

Which MinistryPlatform APIs does the integration use?

Seven parts of MinistryPlatform matter to HubSpot. Most are read into HubSpot; guest forms and opt-outs write back; care data is excluded.

Core

Contacts & households

Contacts · Households tables

Every person starts as a contact and belongs to a household that holds the address and congregation. Contacts become HubSpot contacts; households become HubSpot companies or a household object, so family members stay linked.

  • Contact ID stored on every HubSpot record
  • Household congregation used as campus
  • Household links kept as associations
Core

Participants & journeys

Participants · Milestones Assigned

The participant record shows how a person is involved: participant type such as Guest, Attendee or Member, member status and start date. Milestones assigned along a journey mark next steps taken.

  • Participant type drives lifecycle stage
  • Milestone and date accomplished per step
  • Discontinued journeys stop HubSpot sequences
Core

Groups & serving

Group Participants · Opportunities · Responses

Small groups and serving teams, with each person's group role and start and end dates. Responses to serving opportunities show who raised a hand and whether they were placed.

  • Group role, start and end date
  • Response result shows placement
  • Placed volunteers leave invitation sequences
Core

Events & attendance

Event Participants

Registrations and check-ins for services, classes and events. Participation status records interested, registered, attended, confirmed, canceled and no-show.

  • Participation status values from 01 to 21
  • Time In set by check-in tools
  • Attending Online flag for virtual attendance
Change events

Table webhooks

Administration › Webhooks

Webhooks notify the integration when a record in a chosen table is created, updated or deleted. The notice carries the record ID and change type; the integration then reads the record through the API.

  • Trigger fields and dependent conditions
  • Retries once a minute up to Max Retries
  • Every call logged as a Webhook Invocation
Permissioned

Giving summaries

Donors · Donations tables

Off by default. Where church leadership approves, HubSpot receives summary facts such as whether a household has given and the last gift date, never individual gifts or amounts unless leadership decides otherwise.

  • Leadership signs the giving field list
  • Restricted with HubSpot field-level permissions
  • No gift detail by default
Stays in MP

Care, prayer & notes

Care Cases · Household Care Log · notes

Pastoral care records and private notes stay in MinistryPlatform. The API client user has no access to these tables, so the integration cannot read them.

  • Excluded by security role, not by convention
  • HubSpot links to the person in MinistryPlatform instead
  • Church leadership signs off the exclusion list
03 — Framework

How does the MinistryPlatform HubSpot integration work?

MinistryPlatform webhooks notify a CC-hosted endpoint when approved tables change. The integration layer reads each changed record through the REST API using a client-credentials token, applies the field allowlist, resolves the person to one HubSpot contact and household, and writes in batches. HubSpot guest forms and opt-outs are written back to MinistryPlatform.

MinistryPlatform
REST API tablesContacts, Households, Participants, groups, events
Webhookscreate, update, delete on approved tables
Milestones Assignedjourney steps and dates
Contact preferencesBulk Email Opt Out, Texting Opt In Type
CC integration layer
Webhook receivershared-secret header check, fetch by record ID
Privacy filterallowlisted tables and fields only
Identity resolverContact ID · email · household
Nightly reconciledp_Updated filter catches missed changes
HubSpot writerbatch upserts, associations, replay
HubSpot
Contactsguests, attenders, members, volunteers
Households (companies or custom object)address, campus, family links
Group & serving rolesproperties and lists per group
Attendance & milestoneslast attended, next step taken
Lists, workflows & journeysguest follow-up, next steps
MinistryPlatform → HubSpot (people, households, participation, attendance, milestones)HubSpot → MinistryPlatform (guest forms, email opt-outs)
Principle

MinistryPlatform keeps the church record

People, households, participation, giving and care are recorded in MinistryPlatform. HubSpot holds what communication needs and the history of that outreach.

Principle

Leadership decides what leaves

Church leadership approves every table and field HubSpot may hold. Anything not on the list stays in MinistryPlatform, enforced by the API user's security role.

Principle

Events first, reconcile nightly

Webhooks keep HubSpot current. A nightly read filtered on update time catches anything a missed webhook left behind.

04 — Process

What does MinistryPlatform HubSpot integration setup involve?

Each phase ends on a gate the church signs off before the next begins.

1

Discovery & access

Confirm campuses, participant types, member statuses, group and serving structure, journeys and the HubSpot teams involved. The church creates an API client and a dedicated Client User.

Gate to next phaseSigned system map and API access confirmed
2

Privacy review

List every table and field that would reach HubSpot. Church leadership decides what may be held there and whether any giving summary is included.

Gate to next phaseSigned field allowlist and permission plan
3

Journey design

Map participant types, milestones and serving responses to HubSpot lifecycle stages and next-step workflows.

Gate to next phaseSigned journey map
4

HubSpot setup

Create the custom properties, household model, subscription types, field permissions and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved in sandbox
5

Custom build

Configure table webhooks in MinistryPlatform, then build the receiver, privacy filter, identity resolver, guest form write-back, nightly reconcile and the error replay queue.

Gate to next phaseAll agreed areas syncing in sandbox
6

Backfill

Load current contacts, households and participation, plus an agreed attendance history window, in paced batches.

Gate to next phaseHubSpot counts reconcile to MinistryPlatform views
7

Parallel run & launch

Run for two weeks with workflows paused, review data daily with church staff, then switch on guest follow-up and next-steps journeys.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the MinistryPlatform HubSpot integration sync?

Table and field names follow ACS Technologies' MinistryPlatform documentation where it gives them. Fields described in plain words are confirmed against the church's Swagger page and tables during discovery.

MinistryPlatform fieldHubSpot propertyObjectDirectionNotes
Contacts & households
Contact_IDmp_contact_idContactMP → HSPrimary match key. Unique.
First and last namefirstname, lastnameContactMP → HSMinistryPlatform-owned.
Email_AddressemailContact↔ BothMatch key #2.
Mobile phonemobilephoneContactMP → HSConfirm field in discovery.
Household_ID, Household_Namemp_household_id, household nameHouseholdMP → HSCompany or custom object, agreed in discovery.
Household addressaddress, city, state, zipHouseholdMP → HS
Household Congregationmp_campusContactMP → HSCampus for segmentation.
Participants & journeys
Participant Typemp_participant_typeContactMP → HSGuest, Attendee, Member or church-defined.
Member Statusmp_member_statusContactMP → HSChurch-defined values.
Participant Start Datemp_participant_startContactMP → HS
Milestones Assigned: Milestone, Date Accomplishedmp_last_milestone, mp_last_milestone_dateContactMP → HSLatest step on each journey.
Discontinue Journeymp_journey_discontinuedContactMP → HSStops HubSpot next-step sequences.
Groups & serving
Group Participants: Group, Group Rolemp_groupsContactMP → HSActive groups as a multi-select.
Group Participants: Start Date, End Datemp_in_groupContactMP → HSTrue while any small group is active.
Serving team membershipmp_serving_teamsContactMP → HSGroup types confirmed in discovery.
Responses: Opportunity, Response Datemp_last_serve_interestContactMP → HSRaised a hand to serve.
Responses: Response Resultmp_serve_placedContactMP → HSPlaced or not placed.
Events & attendance
Event Participants: Participation Statusmp_last_event_statusContactMP → HSRegistered, Attended, No Show and so on.
Event Participants: Time Inmp_last_attendedContactMP → HSLatest check-in date.
Attended count in windowmp_attendance_90dContactMP → HSRolled up by the integration.
Attending Onlinemp_attends_onlineContactMP → HS
Guest forms & preferences
HubSpot guest formContact, Household and Participant (type Guest)ContactHS → MPCreated after a duplicate check. Write path agreed in discovery.
HubSpot next-step formResponse to an OpportunityContactHS → MPStaff follow up in MinistryPlatform.
Bulk Email Opt OutHubSpot subscription statusContact↔ BothOpt-out in either system reaches the other.
Texting Opt In Typemp_texting_opt_inContactMP → HSHubSpot SMS honors it.
06 — Auth & API

How are authentication and API limits handled?

Values below come from ACS Technologies' public MinistryPlatform documentation. Items without a published value are confirmed with ACS Technologies.

TopicMinistryPlatformHubSpot
Access modelA church administrator creates an API Client record with a Client ID, Client Secret and Client User. Access to these records is controlled by the Administer Api Clients security role.Private app access token or OAuth 2.0 public app, scoped per object. Custom objects need an Enterprise hub.
InterfacesREST API at the church's /ministryplatformapi path, JSON over HTTPS. Endpoints for tables, procedures, files and communications. Swagger is at /ministryplatformapi/swagger.REST APIs: CRM objects, custom objects, associations, forms, subscription preferences.
AuthenticationOAuth 2.0. Client credentials is the recommended grant for integrations. Endpoints and scopes are listed in the discovery document at /ministryplatformapi/oauth/.well-known/openid-configuration. Token lifetime is set on the API Client record.Bearer token on every call.
PermissionsThe API client inherits the security roles of its Client User. Records the API writes are attributed to that user unless $User is set.Field-level permissions and sensitive data properties by team.
QueriesGET tables/{table} with $Filter, $Select, $OrderBy, $Top and $Skip, or POST tables/{table}/get for long filters. Audit fields include dp_Created and dp_Updated.Search API with filters and cursor paging.
Rate limitsNot published. Confirm with ACS Technologies.Per-10-second burst and daily limits by subscription tier.
Change eventsTable webhooks on create, update or delete, with trigger fields and a dependent condition. The body carries record ID, user and change type only. Retries once a minute up to Max Retries; each call is logged as a Webhook Invocation.Writes are immediate; HubSpot workflows trigger guest and opt-out write-back.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Pastoral care privacyHigh

Care cases, care logs, prayer requests and notes must never reach HubSpot. The API client's security role has no access to them, and church leadership signs the exclusion list.

Giving data is sensitiveHigh

Giving is off by default. If leadership approves a summary, it is restricted with HubSpot field-level permissions and signed before the build.

Duplicate people from web formsMedium

Guest forms can create duplicate contacts and households. The write-back checks email, name and household first, and sends uncertain matches to a staff review queue.

Church-defined valuesMedium

Participant types, member statuses, group types and journeys differ by church. Value tables are signed before workflows are built.

Webhooks carry no dataMedium

A webhook says only that a record changed, so each one costs an API read. Rate limits are not published, so reads are paced and confirmed with ACS Technologies.

Minors and children's ministryLow

Children appear in households and check-in. Minors are excluded from HubSpot marketing lists, and parents are the contact of record.

Opportunities in HubSpot

Timely guest follow-upHigh value

A first-time guest gets a welcome sequence within a day, tailored to their campus, and staff see who has not returned.

Next-steps journeysHigh value

Milestones drive the next invitation: after a membership class, an invitation to a group; after joining a group, an invitation to serve.

Volunteer pipelineHigh value

People who raise a hand to serve are followed up until placed, and placed volunteers stop receiving recruitment asks.

Re-engagementMedium value

Attenders whose check-ins drop off are flagged for a personal note or a re-engagement series.

Campus communicationMedium value

Each campus sends to accurate lists built from household congregation, without exporting from MinistryPlatform.

One opt-out recordMedium value

An email opt-out in either system is respected in both.

Guest to member journey

From first visit to serving, one next step at a time.

The core flow follows a guest into church life. MinistryPlatform records each step; HubSpot sends the right invitation for the next one.

  1. A guest fills in a HubSpot plan-a-visit or connection form; a contact, household and Guest participant are created in MinistryPlatform after a duplicate check.
  2. Check-in records attendance; HubSpot sends a welcome series for the guest's campus.
  3. Milestones such as a membership class are recorded in MinistryPlatform; HubSpot invites the person to a group.
  4. Joining a group and responding to a serving opportunity move the person forward; placed volunteers leave the invitation track.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the mp_ prefix in a MinistryPlatform property group. Household properties sit on companies or a household custom object, agreed in discovery.

Internal nameLabelObjectTypeSource / logic
mp_contact_idMinistryPlatform Contact IDContactSingle-line textContact_ID; unique
mp_household_idMinistryPlatform Household IDContactSingle-line textHousehold_ID
mp_campusCampusContactDropdownHousehold congregation
mp_participant_typeParticipant TypeContactDropdownGuest, Attendee, Member, church-defined
mp_member_statusMember StatusContactDropdownChurch-defined values
mp_last_milestoneLast MilestoneContactDropdownMilestones Assigned
mp_last_milestone_dateLast Milestone DateContactDateDate Accomplished
mp_groupsActive GroupsContactMultiple checkboxesGroup Participants with no end date
mp_serving_teamsServing TeamsContactMultiple checkboxesServing group memberships
mp_last_attendedLast AttendedContactDateLatest Event Participants Time In
mp_attendance_90dAttendance (90 days)ContactNumberCount of attended events
mp_texting_opt_inTexting Opt In TypeContactDropdownContact texting preference
09 — Scope builder

Interactive scope builder

Choose the areas and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
MinistryPlatform × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

MinistryPlatform HubSpot integration FAQ

Does MinistryPlatform integrate with HubSpot?

Yes. Campaign Creators builds a custom integration using MinistryPlatform's REST API, documented at each church's own Swagger page. A church administrator creates the API client, with no vendor approval needed to get started.

What data syncs between MinistryPlatform and HubSpot?

Contacts and households sync to HubSpot contacts and companies, and participant type, member status, milestones, groups, serving placements and event attendance flow into HubSpot as well. HubSpot guest forms and opt-outs write back to MinistryPlatform, and giving summaries sync only if church leadership approves.

Which system owns which data?

Each record has one owner. MinistryPlatform owns people, households, participation, groups and attendance; HubSpot owns guest and next-step forms. Pastoral care, prayer requests and private notes stay in MinistryPlatform entirely, since the API client's security role has no access to those tables.

What does setting up the MinistryPlatform HubSpot integration involve?

Seven phases, each closed by a church sign-off: discovery and access, a privacy review of every field that would reach HubSpot, journey design, HubSpot schema setup in a sandbox, building the custom integration layer, backfill, and a two-week parallel run before guest follow-up and next-steps journeys go live.

How long does the integration take and what does it cost?

Timeline and cost depend on the tables, fields and journeys in scope, and whether a giving summary is included. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.