MuseRelay can send your customers’ messages to an external automation tool —n8n, Make or any other that receives webhooks— so your own flow processes and answers them. It’s a powerful feature, and that’s why we handle it carefully: it’s enabled on request and only with servers in Europe.
On request, from the Pro plan. Write to webmaster@muserelay.com telling us what you want to automate and with which tool; our team reviews it and enables it on your account.
What you can do
On a channel
Messages arriving on that channel go to your flow instead of the AI agent. Your flow decides what to answer and replies through MuseRelay.
- Set it up on the channel → AI agent tab → External automation.
- When turned off, the channel goes back to what it had: your AI agent or your team.
On an AI agent
The agent keeps talking and can call your flow like any other tool: check an order, create something in your ERP, notify another system…
- Set it up on the agent → tools → n8n.
Why it’s enabled on request
At MuseRelay your conversations are stored on servers in the European Union. When you send them to an external tool, they leave MuseRelay, and the GDPR applies to that journey:
- International transfer. Sending personal data to a server outside the European Economic Area requires a country with an adequacy decision or safeguards such as standard contractual clauses, plus informing the people affected.
- Who is responsible for what. You are the controller of your customers’ data; MuseRelay is the processor and can only send it where you instruct us in writing.
- What we promise. We say your data stays in Europe. If a channel sent it to another continent without control, that would no longer be true.
That’s why a switch isn’t enough: we want to know what is being automated and with which tool before opening it.
The controls we apply
- Manual activation. Only our team enables it, for your organisation or for specific users.
- Recorded consent. When enabling it or changing the address, you confirm you are the controller and have a data processing agreement (DPA) with the provider. It’s recorded with date, user and IP.
- HTTPS only. Data travels encrypted.
- Server in Europe. We check the country of the server that receives the data: only the EU/EEA, the United Kingdom and Switzerland are allowed. If its location can’t be determined, it isn’t allowed.
- Documented exceptions. If you need another country, it can only be authorised with a DPA and the GDPR safeguards documented.
We check where the server is, not who the company is. A service hosted in Europe by a company from elsewhere may be subject to its home country’s laws. Choose providers that offer a DPA and clear safeguards, or install the tool on your own European server.
Which tools you can use
Any tool that can receive an HTTPS webhook and reply, as long as the receiving server is in the EU/EEA, the United Kingdom or Switzerland:
| Tool | What to keep in mind |
|---|---|
| n8n | You can install it on your own European server, or use n8n Cloud, which is hosted in Frankfurt. |
| Make | Choose a European (EU) region when creating the organisation. |
| Zapier | Not for now It stores and processes data in the US and doesn’t offer EU-only storage. |
| Activepieces, Node-RED, Windmill | Can be installed on your own European server. |
| Others (Pipedream, Power Automate…) | It depends on where their servers are: check with the provider. |
What if your tool doesn’t comply?
Tell us what you need. If your automation can’t comply with the GDPR, we can look at building it inside MuseRelay. Our plan is to have more and more native tools, all in Europe: that’s how the booking calendar and the ticket system were born, working without depending on third parties.