Two way
Stripe starts the integration and changes made in ServiceM8 flow back into Stripe as well.
- You pick whether Stripe or ServiceM8 leads in a conflict
- Changes on either side travel
- Nothing bounces back and forth
CRM Connector Platform
ServiceM8 and Stripe, one contact list
Stripe takes payments online, ServiceM8 runs jobs and the schedule in the field. CRM Connector keeps the contacts the same in both, so nobody retypes a record.
- Restricted api key for Stripe
- Either system can lead
- 7 day free trial
Contacts, two way or one way
- Contacts
At a glance. Contacts stay the same on both sides. Below: which field matches which, and what every change does.
Your choice
Two way or one way
Keep both systems identical, or let one feed the other. You decide per record type.
One way
Stripe feeds ServiceM8 and ServiceM8 changes stay in ServiceM8.
- Stripe stays the source of truth
- ServiceM8 always has the latest customers
- Switch to two way later
Fine tune it:Everyone, customers only or leads onlyEvery 30 minutes up to every 3 days
Record by record
What travels, and what each change does
Pick a record type and the system where a change starts. On the left, which field matches which and when it travels; on the right, what that change does on the other side.
Starts in
Fields- Client nameBoth waysDescription
- Contact first nameWhen createdName
- Contact last nameOnly in ServiceM8Not in Stripe
- Contact emailBoth waysEmail
- Contact mobileBoth waysPhone
- Address line 1Both waysAddress line 1
- Address line 2Both waysAddress line 2
- City, state, postcodeBoth waysCity, state, postal code
- CountryBoth waysCountry
- Has completed jobsEach works it outPaid invoices
- Not in ServiceM8Only in StripeSource
It happens in ServiceM8, then in Stripe
A new contact
Looked for in Stripe on the exact email and updated when found; otherwise created, with first and last name joined into one name.
Company, email, phone, address and country change
The same change is made to the Stripe customer on the next sync.
Name changes later
Not carried: Stripe keeps one name, set when the customer is created.
- Some fields travel once, when the record is created: Stripe keeps one name, set when the customer is created.
- Before anything is created the other system is searched first, so nothing is created twice.
How a sync runs
One sync, step by step
What happens every time the integration runs, in the order it really happens. Pick which system leads and watch the records move.
Which system leads?
Connections
CRM
Step 1 of 7
Both connections are checked
Credentials for ServiceM8 and Stripe are checked and sign in tokens refreshed automatically. If a connection was removed on either side, the integration pauses and you get one message with a reconnect button.
Conflicts
When both sides changed the same record
- For each two way record type you choose whether ServiceM8 or Stripe leads. The leading side always runs first in a sync.
- It only matters when the same record changed in both systems between two syncs. Every other change simply travels.
- A record is never moved backwards by a sync: a paid invoice is not reopened, a decided quote is not undecided.
Between two syncs
The phone number of the same client is changed in both systems
Leading system
+1 415 555 0101+1 415 555 0199Two different values. Run the sync to see which one both systems end up with.
Good to know
What is particular to this pair
What holds for ServiceM8 or Stripe on its own is on its own page.
- Stripe starts the integration
- It can only be the source; ServiceM8 changes still flow back on two way.
- Name on create
- Later changes stay in the system where they were made.
- Contact last name stays in ServiceM8
- Stripe has no such field.
FAQ
Questions about ServiceM8 and Stripe?
Every answer below is true for the app as it runs today. If something is not covered, ask us and we will answer in plain words.
- Can I sync ServiceM8 and Stripe both ways?
- Yes. Stripe starts the integration, and on a two way route changes made in ServiceM8 flow back into Stripe.
- What syncs between ServiceM8 and Stripe?
- Contacts. Invoices, quotes and jobs are not offered between these two.
- How does Stripe connect?
- With a restricted api key from the Stripe Dashboard, with write access to customers and read access to invoices, quotes and products.
- Does a changed name reach the other system?
- Name travels when the record is created, because stripe keeps one name, set when the customer is created. A later change is made in both systems.
- Can I sync only paying customers?
- Yes. Pick customers only: in ServiceM8 that is completed jobs, in Stripe paid invoices.
- Will it create duplicates?
- No. Before anything is created in ServiceM8 or Stripe, the platform looks for the same record first and updates that one instead. Records synced before stay linked.
- What if the connection to ServiceM8 or Stripe drops?
- The platform notices on the next sync, pauses the integration and sends you one message with a reconnect button. Reconnecting takes one step, and syncing picks up where it left off without creating anything twice.
- How often does it sync?
- From every 30 minutes up to every 3 days, depending on your plan. Every plan includes a 7 day free trial.
Ready to connect ServiceM8 and Stripe?Start your 7 day free trial
Sign in to ServiceM8 and Stripe, pick which one leads or sync one way, confirm what syncs, and watch the first sync run.