A sales manager wants to know each morning which customers have not replied to a quote. An owner wants the CRM, the shared inbox and the team chat to stop being three separate places. Meta's personal agent, Muse, can reach more than 9,000 apps through the Zapier connector from a chat conversation.¹
The question is no longer "what can it do?" but "what should it be allowed to do in my business?" Once an agent can read your records and act in other tools, the limits are your decision.
It covers three decisions to make before you switch anything on: which records Muse may read, which actions wait for a person, and who checks and fixes mistakes.
What the Meta Muse Zapier integration actually does
Muse is Meta's personal agent. On its own, it comes with about 40 built-in connectors, including Google Workspace, Dropbox and Notion.¹ Through Zapier MCP, Muse can reach more than 9,000 apps and 40,000 actions once a user authorises it.² These include apps Muse does not support itself, such as HubSpot, Zendesk, Airtable and QuickBooks.¹
Zapier MCP connects Muse to apps and actions through Zapier.² Muse can take one-off actions across more than 9,000 apps through Zapier.³ Muse can build a workflow as a Next Gen Zap.³
When we connect applications for a client, we also plan how the connection will be tested, handed over and maintained.⁴ From a chat conversation, Muse can access connected apps and set up a workflow.¹,³ That is why the limits need to be decided by someone in the business, not left to defaults.
You may not see the integration yet because its availability depends on Meta's rollout and user authorization.² Test each capability with your own accounts before relying on it.
Why an agent connected to your business tools is different from a chat window
A chat window answers and then stops. You copy the text and decide what to do with it. An agent connected to your business tools works differently, which is the main point of what an AI system is beyond a chatbot.
Muse is built to handle everyday tasks by connecting to a person's apps and services, including email and calendars.⁵ It can keep working after the app is closed, reach the accounts that have been connected and take real actions inside them.⁶ Its email connector can read messages and also send them, and its browser can fill in forms.⁶ Through Zapier, it can choose the apps, connect the steps of a workflow and deploy it to run on its own.³
So it helps to have one word for the part that needs care. A write action is any step that sends, posts or changes a record: an email to a customer, a message in a team channel, a new deal stage in the CRM. A guide to Muse lists Zapier among connected-app automations where some actions write.⁶
Reading is rarely where problems start. Writing is where a mistake reaches a customer or changes data your team relies on.
Decide which records it may read
Start with a list on paper, not in the settings. Write down the records each task really needs. For a follow-up list, that might be CRM deals and last-contact dates. For a quote reply, it might be the price sheet and the shared inbox. Anything not on the list stays unconnected.
You can limit Muse to the specific apps and actions you approve.² A sensible default is read-only, which means the agent can look at records but cannot edit or delete them. Zapier's own example gives Muse read-only access to a CRM while allowing it to post in Slack.² Permissions for specific apps and actions can be adjusted later inside Zapier.¹
Then narrow the time window. One guide's sample prompt suggests limiting email context to the last seven days.⁶ An agent we build only reaches the tools and data its task needs.⁴
Before connecting customer records, read Meta's and Zapier's terms on what data is kept, for how long and who can see it. If customers also reach you on WhatsApp, do not plan around it until you see it among the apps you can connect in your own settings.
Connected apps continue to apply their own permissions and API limits.² An API limit is a cap on how many requests a tool will accept in a given time, so a busy setup can reach it.
In the knowledge systems we build, people only get answers from material they are allowed to see.⁴ Check this with a test request rather than assuming it.
Decide which actions wait for a person
Sort every action into three groups. Read: look up a deal, open a price sheet, find an order. Draft: prepare a reply, a list or a row, but do not send or save it. Send, post or spend: anything that leaves the business or changes a record others rely on.
Meta says nothing is published, sent or spent without approval.⁶ Muse asks for confirmation before actions it flags as needing review.¹ Your own rule can be simpler: every action in the third group waits for a named person, at least for the first weeks.
This matters most for workflows that run on their own, because Muse can deploy a workflow to run autonomously.³ A workflow that only prepares drafts is safe to leave running. A workflow that sends needs a clear reason to run without a check, and a person who made that decision. Treat a deployed workflow differently from a one-off request: decide before deploying which of its steps send anything, and do not assume each run will ask you first.
Permissions for specific apps and actions can be changed later in Zapier.¹ We describe the same approach in more detail in building AI workflows with human review.
Warning
Name who checks mistakes, and where they look
Every connected tool needs one person who owns it. Not "the team", but a name. For the CRM, it might be the sales manager; for the shared inbox, the office manager. That person handles exceptions: a wrong customer on a list, a message that should not have gone out, an action that failed.
They also need somewhere to look. Zapier MCP offers workspace controls and an activity history that shows what was done.² Agree how often it is read. For a small team, daily in the first two weeks and then weekly is a reasonable schedule. Keep a short note of each error and what was changed.
Keep a fallback during the trial. Run your usual process alongside, so a missed message or failed action is still caught, and agree that anything incomplete or unclear goes back to a person instead of being guessed.
Access is personal. Each user connects through their own Zapier account, and that user's connections and permissions decide what Muse can reach.² Review each person's Zapier connections and permissions, since those govern the apps and actions they can access.² When someone leaves the company, their connections must be removed too.
Sign-in is handled through Zapier, so nobody needs to give Muse an API key or a password directly.¹ Make it a written rule anyway: no passwords are ever typed into the chat.
An example: a morning follow-up list for the sales team
Here is a small, low-risk first use. Consider this question: which customers have not yet replied to the quote they were sent? If sales follow-ups that slip are a familiar problem, this is a good place to begin.
It follows Zapier's own example: read-only access to the CRM, permission to post in Slack, and a request to tell the team who needs a follow-up.² If your team already connects sales tools with messaging tools, the pattern may feel familiar. The difference here is that a person checks the list before it is posted.
Trigger
Manager asks for today's follow-ups
Each morning the sales manager asks Muse which customers need a follow-up.
Prepared by the system
CRM read, read-only
In Zapier's example, Muse can have read-only access to the CRM.² It cannot change records.
Prepared by the system
List prepared
Muse could use read-only CRM access to tell the team which customers need a follow-up.²
Checked by a person
Sales manager checks
The manager removes wrong entries and approves the post. Errors are noted for the named owner of the setup.
Result
List posted in Slack
The approved list appears in the sales channel. An activity history is available through Zapier MCP.²
In Zapier's example, Muse has read-only CRM access and permission to post in Slack.² The worst likely outcome is a customer wrongly included on an internal list, which the manager removes before posting. Once this works well, a similar setup could prepare a short brief before a large call, with attendees, account details, recent emails and news.³
The same pattern can suit order emails copied into a sheet: the row is prepared, a person checks it, and an order with a missing quantity or date goes back to the customer with a question.
What setup and upkeep take, and when a built system fits better
When planning the effort, consider which tools to connect, the state of their records and the time someone will spend reviewing permissions and outputs. A CRM with missing last-contact dates will give a poor follow-up list, however good the agent is. If you already run a fixed connection between two tools, such as a Salesforce Slack integration, list it too, so the same record is not handled twice.
Watch how much of your Zapier task allowance the workflow uses.¹ Muse's activity through Zapier draws on the same task allowance your existing Zaps already use.¹ Connected apps still apply their own API limits.² Run a trial and check how many tasks it used before deciding.
Test the language as well. If your customers write in Latvian, Lithuanian, Estonian or Russian, check real drafts in each language before anything is sent. Names, grammatical endings and polite forms of address are where errors tend to appear first.
A manager could try one-off actions through Muse and Zapier.³ When a process runs across a whole team every day and needs a review queue, sources for every answer and one owner for exceptions, a system built around that process can fit better. Consider whether a system built around that process would fit better.
Write down which records each task needs, and connect nothing else.
Give read access first and add write actions one at a time.
Decide which sends, posts or changes wait for a named person.
Choose one person per tool and agree how often they read the activity history.
Try a week of real requests in every language your team uses before relying on the output.
Frequently Asked Questions
Does Muse need my passwords to connect to my business apps?
No. Sign-in is handled through Zapier, so Muse is never given an API key or password directly.¹ Each user connects through their own Zapier account, and that user's connections and permissions govern what Muse can reach.²
Can Muse send emails or post messages without my approval?
By default, Muse asks for confirmation before actions it flags as needing review.¹ Meta says nothing is published, sent or spent without approval, but the approval card only shows what Muse proposes.⁶ Read the content before you approve, because the email connector can send as well as read.⁶
Can I change what Muse is allowed to do after connecting it?
Yes. Permissions for specific apps and actions can be changed later in Zapier.¹ A careful way to begin is read-only access to records such as your CRM, as in Zapier's own example, adding write actions one at a time.²
Is the Meta Muse Zapier integration available to my business yet?
It is being rolled out in stages, and availability depends on Meta's rollout and on each user authorising it.² We cannot promise a date. Check your own Muse settings to see whether the Zapier option has appeared.
Sources (6)
- Zapier Connects Meta Muse to 9,000+ Apps — inite.ai
- Meta Selects Zapier as Named Connector Inside Muse — zapier.com
- Zapier is now a connector in Muse! Just tell your agent to build you... — linkedin.com
- lindevo.com
- Everything new coming to Meta's AI agent Muse TechCrunch — techcrunch.com
- 100 Best Meta Muse Prompts For Work (2026) AI Agents Library — aiagentslibrary.com
Have a process you'd like to talk through?
Book a call (opens in a new tab)