> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation platforms

> Connect Voiceflow to automation platforms to run approved workflows and use their results in customer conversations.

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](/docs/guides/integrations/automation/run-a-workflow)** — connect a confirmed request to the intended automation and check the agent's answer.
- **[Handle pending automation requests](/docs/guides/integrations/automation/handle-pending-requests)** — return a truthful receipt while approval or background work continues.
- **[Investigate a failed automation](/docs/guides/integrations/automation/investigate-failures)** — find the original execution and reconcile its side effects before retrying.
- **[Create new integration](/docs/guides/integrations/create-new-integration)** — connect a platform that does not yet have a provider manual.

## Platforms

- **[Power Automate](/docs/guides/integrations/power-automate/overview)** — Submit a protected approval request and return a pending receipt.
- **[Zapier](/docs/guides/integrations/zapier/overview)** — Call a configured MCP action or start an existing Zap.
- **[MuleSoft](/docs/guides/integrations/mulesoft/overview)** — Call an approved API backed by your Mule business service.
- **[Boomi](/docs/guides/integrations/boomi/overview)** — Invoke a deployed process and return its output document.
- **[Workato](/docs/guides/integrations/workato/overview)** — Call an activated API recipe under a scoped client key.
- **[n8n](/docs/guides/integrations/n8n/overview)** — Run a published workflow through an authenticated webhook or MCP tool.
- **[Make](/docs/documentation/build/tools/make-tool)** — Run an existing scenario through the packaged action.

- **[UiPath](/docs/guides/integrations/uipath/overview)** — Start an approved robot job, check its output or use a hosted MCP tool.

## Choose the result your agent needs

| Request | Connection behavior | What the agent can say |
| --- | --- | --- |
| Look up an order or complete a short action | The workflow returns the actual business result during the call. | Report the result after checking the current response and required fields. |
| Record work for another team | The workflow returns the reference of a successfully saved request. | Confirm that request was recorded; do not claim the later work happened. |
| Wait for approval or longer processing | The workflow acknowledges receipt or returns a pending reference. | Explain that it is pending and use the workflow's agreed status or notification route. |

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](https://creator.voiceflow.com), 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](/docs/developers/tools/execute) is separate from deployment.

General [API tools](/docs/documentation/build/tools/api-tool) and [MCP tools](/docs/documentation/build/tools/mcp-tool) retain their shared feature documentation. Here Voiceflow is the client of the external MCP server. [Voiceflow MCP servers](/docs/mcp/overview) connect development clients to Voiceflow in the other direction.
