Automation platforms connect the business systems behind a customer or employee request. Your Voiceflow agent calls an approved workflow; the external platform owns its app connections, processing and execution history. Choose the platform your team uses, then prepare its endpoint, credentials and completion behavior with the workflow owner.
Guides
- Run a cross-system workflow — connect a confirmed request to the intended automation and check the agent’s answer.
- Handle pending automation requests — return a truthful receipt while approval or background work continues.
- Investigate a failed automation — find the original execution and reconcile its side effects before retrying.
- Create new integration — connect a platform that does not yet have a provider manual.
Platforms
-
Power Automate — Submit a protected approval request and return a pending receipt.
-
Zapier — Call a configured MCP action or start an existing Zap.
-
MuleSoft — Call an approved API backed by your Mule business service.
-
Boomi — Invoke a deployed process and return its output document.
-
Workato — Call an activated API recipe under a scoped client key.
-
n8n — Run a published workflow through an authenticated webhook or MCP tool.
-
Make — Run an existing scenario through the packaged action.
-
UiPath — Start an approved robot job, check its output or use a hosted MCP tool.
Choose the result your agent needs
An HTTP 200, an MCP call or a connected-account indicator does not establish that every downstream action completed. A timeout can leave the outcome unknown. Define that contract before enabling writes.
Work in Voiceflow
In Agent studio, add the approved action under Agent → Global tools or invoke it at a fixed point in a Workflow. The provider manual explains its actual setup and result handling. Developers use the same manual’s Code view to create resources, execute tests and attach the tool; standalone tool execution is separate from deployment.
General API tools and MCP tools retain their shared feature documentation. Here Voiceflow is the client of the external MCP server. Voiceflow MCP servers connect development clients to Voiceflow in the other direction.