use case · sync

Two systems, one customer record.

A job is paid in ServiceM8. The customer is updated in Klaviyo, tagged for a follow-up, and logged. Your existing customers come across in batches first. Every night you get the counts.

sprigr · new workflow listening
Example run · 41 actions hover the gate to approve it yourself
what runs, what stays yours
set it up in a sentence

When a ServiceM8 job is paid, update the customer in Klaviyo, tag them for a follow-up, and send me the numbers each night.

the story

Every job event, mirrored where your marketing lives.

Your job system knows who you worked for, what you did and when. Your email platform does not, so follow-ups are guesswork. Sprigr listens for job created, quote sent, job completed and job paid, updates the customer's profile and properties in Klaviyo, adds the right tag or list, and writes a line in the sync log so nothing is done twice. Before the live sync starts, a checkpointed first pass brings your existing customers across in batches of forty, switches itself off when it is done, and tells you the counts. If a customer has no email, it says so rather than guessing.

plugs into
keeping systems in step

Name the two systems. Sprigr keeps them in step.

One sentence about the events and the tags. Live in under an hour.