To send your leads from Zapier, Make or n8n to an AI agent, connect the tool to a Muzau agent. Every lead your scenario receives, from an ad, a page or a spreadsheet, is passed to the agent: it writes a first message using what your business knows, then follows the conversation. Depending on your settings, that message goes out on its own or waits for you in “To approve”. Without these tools, the agent also has its own entry address, secured by a key.
Many leads do not arrive by email. They fill in an ad form or sign up on a page, and Zapier, Make or n8n file them somewhere: a spreadsheet row, a record, a notification. The scenario does the transport, and nobody asked it to write.
So the lead waits in its row. They left their address an hour ago, then a day ago, and may have asked elsewhere. Your team keeps the meeting, the proposal and the relationship; it is the first message and the upkeep of what follows that the agent takes on, alongside them.
Zapier, Make and n8n connect in Muzau's tools: the last step of your scenario passes the lead to the agent, with their name, their email address and what they asked for. For any other tool, the agent also has its own entry address (a webhook), secured by a key. Muzau prepares the steps to follow for the tool, or a complete message for the person who handles it. A form that already sends an email needs no scenario: see contact form requests.
The request passed on by the scenario is handled as soon as it arrives, day or night. The agent writes to the lead using the Brain, what Muzau knows about your business: your offers, prices, lead times, rules and tone. It also looks up the page of your site that answers a specific question. If it cannot find one, it tells the lead so and the question comes back to you. The message goes out from your business's address at Muzau, or from your connected inbox, and by default notes at the bottom that it was prepared by an AI.
For the agent, the fields sent by the scenario are information, never an order: the recipient is set by the platform, and an instruction slipped into a field cannot make it write to someone else. The agent does not reply to a “no-reply” or notification address. A person on your “do not contact” list gets no more follow-ups, whichever agent it is.
On the Autonomy page, you choose whether the agent writes to leads on its own or submits each message to you, waiting in “To approve”. Every request passed on is filed in the agent's tracking file: an agent that keeps none cannot receive any. When the lead replies, the agent carries on the conversation. When a request is beyond it (a callback, a decision, information it does not have), it comes back to you in “To do”. An agent that qualifies leads gathers the information you have chosen, and follows up on what is missing, at D+2 then D+4 for example, if you ask it to.
With or without an agent at the end, a lead scenario is judged by what it does not lose:
Zapier, Make or n8n? Zapier is the quickest to pick up and connects a very large number of apps. Make draws the scenario as a diagram, with branches, and gives more control. n8n can be installed on your own server, to keep the data with you, and takes a bit more technical skill. For the agent, the choice changes nothing: it receives the same lead. For the reply itself, see answering inbound leads.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.