1. The short answer
As of October 25, 2026, Zapier is a live connector in Muse. It was still listed in the October 15 in app check, which counted 54 connectors in the web app, with no October change since it went live on September 29, 2026. One connector opens more than 9,000 apps and 40,000 actions to Muse through Zapier MCP, which is the system Zapier uses to let an AI agent call its apps. Instead of waiting for Meta to add each tool you use, Zapier carries them in. Rollout is staged, so some accounts see it before others, and you choose which apps and actions Muse can touch.
Here is the honest version. Zapier is the connector that changes the whole counting problem on our connectors list. The named list in the app counts 54 connectors. The reachable list through Zapier is far larger, and it includes the tools Meta has never named, like HubSpot and Salesforce, which appear on no Muse list we have checked. If your business runs on a tool Meta has not added, Zapier is the honest workaround. The rest of this guide covers how to connect it, how to choose the scope, and the workflows worth building first.
Muse is invite only right now. Need an invite code? Click here to grab one free from the community pool. Waiting on a launch in your country? Join the waitlist and we will send you a fresh code on launch day. Muse is available in the United States, Canada, and Japan.
2. What you need
- Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
- A Zapier account. The connector runs through Zapier, so you need an account there and the apps you want to use connected inside Zapier first.
- A short list of the apps Muse may touch. Decide this before you connect. Start with two or three apps that matter, not everything you own.
- Approvals set to ask me. Anything that creates, updates, sends, or spends must wait for your tap. Set this before the first workflow runs.
- One workflow in mind. Pick the single most repetitive job you hand off first, like logging new leads or turning form submissions into tasks. One working workflow beats ten half built ones.
3. How to connect it, step by step
The connection is quick. The scoping is the real work, so do not rush past step four.
- Connect your apps inside Zapier first. Open Zapier, connect the two or three apps you want Muse to reach, and confirm each one works there. Muse can only reach what Zapier can already reach.
- Open Muse and go to Settings. The connectors list lives there. If Zapier is not listed, your account has not received it yet, because rollout is staged. There is nothing to install and nothing you broke. Check again in a few days.
- Find Zapier in the connectors list and open it. Sign in with your Zapier account when asked and grant the access Muse needs to call Zapier on your behalf.
- Choose which apps and actions Muse can use. This is the step that decides your risk. Allow only the apps on your short list, and only the actions each workflow needs. If a workflow only reads your CRM, do not allow it to delete records. Least access is the rule.
- Set approvals to ask me. In Muse settings, set approvals so that anything that creates, updates, sends, or spends waits for you. Reading and drafting can run free. Changing things cannot.
- Test with a read only request. Ask Muse to list the last five items in one connected app, like your latest form submissions or your newest CRM contacts. Check the answer against the app itself. If it matches, the connection is good.
- Run one small workflow end to end. Pick the single workflow from step one of the list above and run it with a real item, watching every step. Approve each action the first time. Once it behaves, let it run.
Copy this prompt
You are helping me run my business through Zapier. Use only the apps I have allowed: [list your apps here]. Rules: you never create, update, delete, send, or spend anything without my explicit approval. You read, summarize, draft, and shortlist. I approve every change. My business: [what you sell, who buys from you] Every morning, do this in order. 1. Check my [form tool] for new submissions from the last 24 hours and list them with name, contact, and what they asked for. 2. For each new submission, check whether that person already exists in my [CRM tool]. New people get a draft welcome reply in my voice. Show me the drafts. Do not send anything. 3. Create a task in my [project tool] for each new submission that needs follow up, with the contact and the ask in the task. 4. End with a count: how many new, how many already known, and anything that looks urgent.
4. What it actually opens up
Zapier is a multiplier, not another app. One connection carries thousands of tools into Muse, and the value is in which ones you pick, not in how many exist.
Your CRM, even the ones Meta never named
Salesforce and HubSpot appear on no Muse connector list we have checked as of October 25, 2026. Both are on Zapier. Through Zapier, Muse can look up a contact, log a new lead, update a deal stage, and draft the follow up, all from the same conversation where it read your mail. This is the single most useful thing Zapier opens for a small business, because the CRM is where the money trail lives and Meta has not connected it directly.
Project tools and task lists
Asana is a native Muse connector, and Todoist and Linear are live in the app too. Zapier adds the rest of your stack: the project tool your clients insist on, the task list your team actually uses, the tracker nobody wants to open. Muse can turn a form submission into a task, a thread into a ticket, and a Monday morning into a list of what is overdue and who owns it.
Forms, sheets, and the intake pipe
Most small businesses run on an intake pipe: a form on the site, a sheet that collects the answers, and a human who reads the sheet. Zapier lets Muse sit on that pipe. New submission arrives, Muse reads it, checks the CRM, drafts the reply, and creates the task. The human reads the drafts and approves them. The pipe still works the same way. It just stops needing you to be the one reading the sheet.
What MCP means in plain words
Zapier MCP is the system that lets Muse call Zapier apps. You do not need to understand the protocol to use it. Think of it this way: Zapier already knows how to talk to 9,000 plus apps. MCP is the door it opens for an AI agent to walk through and use those connections. Your job is not the protocol. Your job is the list of apps on the other side of the door and which actions each one is allowed to do.
5. Workflows worth building first
Build one workflow at a time, and build the boring ones first. The flashy automations fail. The boring ones save an hour a week each, and they compound.
- New lead, logged and answered. A form submission arrives. Muse checks the CRM, logs the new lead, drafts a welcome reply in your voice, and creates a follow up task with a date. You approve the draft and the task. Nothing else changes in your week, except the leads stop sitting unread.
- The daily intake digest. Every morning, Muse reads the last 24 hours of form submissions, support messages, and new CRM entries, and gives you one list: new, already known, urgent. This replaces three separate checks with one read.
- Invoice paid, books updated, thank you sent. When a payment lands, Muse updates the tracker, drafts the thank you note, and flags anything that looks off, like a payment that does not match any invoice. You approve the note. The books stay current without a weekly reconciliation session.
- Meeting notes into tasks. After a call, Muse takes the notes and turns each decision into a task in your project tool, assigned to the right person with the right date. The meeting stops evaporating the moment it ends.
Notice what these four have in common. Each one starts with something arriving, checks it against something you already have, drafts the response, and waits for you. None of them let Muse act alone on money or customers. That pattern, arrive, check, draft, approve, is the safe shape for every Zapier workflow you build after these.
6. What to watch for
Zapier went live on September 29, 2026, and rollout is staged, so the first thing to check is whether your account has it at all. As of October 25, 2026, that is still the position: Zapier was still listed in the October 15 in app check, and no October update has changed its status. Open Settings, open the connectors list, and look. If it is not there, your account has not received it yet. Check again in a few days. There is nothing to install and nothing you broke.
Scope is the second thing, and it matters more than the connection. Every app you allow is an app Muse can act in. Allow two or three apps per workflow, not your whole Zapier account. If a workflow only needs to read your CRM, do not allow it to delete records. Review the allowed list once a month and remove anything you no longer use.
Zapier has its own usage limits and plans, and heavy workflows consume them. Check what your Zapier plan covers before you build a workflow that runs every few minutes all day. A workflow that checks for new items once a morning costs far less than one that polls all day, and for most small businesses the morning check is enough.
Verify what Muse did, especially in the first weeks. Open the CRM entry it created, read the task it added, check the draft before you approve it. A wrong entry acted on fast is worse than a slow entry you verified. Over a few weeks, once the entries keep matching, you can trust the loop and check less often. Trust is earned by the loop, not granted on day one.
Get started
Connectors need Muse first. Every tool on this page plugs into a Muse account, and accounts still open with an invite code in the United States, Canada, and Japan. Get a code from the pool, connect Zapier, and start with one workflow. Outside the launch countries, the waitlist holds your place.
Get a code Join the waitlistFrequently asked questions
- What is the Zapier connector in Muse?
- It is one connector that opens more than 9,000 apps and 40,000 actions to Muse through Zapier MCP. Instead of waiting for Meta to add each tool you use, Zapier carries them into Muse.
- Do I need a Zapier account?
- Yes. The connector runs through Zapier, so you need an account there, with the apps you want to use connected inside Zapier first. Muse can only reach what Zapier can already reach.
- Can Muse use every Zapier app?
- No. Muse can use only the apps and actions you allow. Choose two or three apps per workflow and only the actions each workflow needs. Least access is the rule.
- Is Zapier live for everyone?
- No. Zapier went live on September 29, 2026, and rollout is staged. As of October 25, 2026, it was still listed in the October 15 in app check, and no October update has changed that. If it is not in your connectors list yet, your account has not received it. Check again in a few days.
- Does Zapier replace the native connectors?
- No. Native connectors like Shopify, Stripe, and Notion connect directly to Muse. Zapier carries the tools Meta has not named, like HubSpot and Salesforce, and it is the honest workaround for those.
- What if Muse does the wrong thing in one of my apps?
- Check the app it touched first, fix the entry there, then narrow what Muse is allowed to do. Keep approvals on ask me for anything that creates, updates, sends, or spends, so a wrong action waits for you instead of landing.
Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.