Zapier connects Mucka to thousands of other apps without anyone writing code. You build a "Zap": when this happens in one app, do that in another.
You'll need a paid Mucka plan and a Zapier account (Zapier has a free plan). Only someone who can manage the workspace can connect it.
What Zapier can do in Mucka
- Add a client. If the same person comes through twice, say from a form they filled in twice, Mucka matches them to the client you already have instead of making a second one.
- Book a job. It lands unscheduled, or pencilled in if the Zap sends a time. It's never confirmed, so your customer isn't told they're booked in until you confirm it yourself.
- Add a note to a job.
- Draft a quote. It sits in your quotes as a draft. Mucka never sends it; you check it and send it when you're happy.
Zapier can't send anything to your customers. No emails, texts or quotes go out because of a Zap. That's deliberate.
What Mucka can tell your other apps
Zapier can start a Zap when:
- a new client is added
- a job is booked
- a job is finished
- a customer accepts a quote
- an invoice is paid
For example, add every new client to your Mailchimp list, or post in Slack when a quote is accepted.
Clients and jobs you import from another system don't set these off, so moving your records into Mucka won't flood your Zaps.
The other way round: Mucka using your apps
This article is about your other apps sending things into Mucka. Mucka can also use your other apps for you, like adding a lead to a Google Sheet when you ask. That's set up separately: see Let Mucka use your other apps.
Connecting
- In Mucka, go to Settings → Integrations → Zapier and tap Set up a Zap.
- In Zapier, choose Mucka as the app and sign in when asked.
- If you're in more than one Mucka workspace, choose which one to connect.
The connection acts as you, with your permissions. If you can't see invoices in Mucka, neither can your Zaps.
Disconnecting
In Settings → Integrations → Zapier you can see every connection, who made it, and when it was last used. Tap Disconnect and its Zaps stop straight away.
A connection also stops by itself if the person who made it leaves the workspace or is suspended, or if the workspace moves to the free plan.