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

# Confirm action

> Ask the participant to approve the specific tool action that will run next.

Use **Confirm action** before an integration makes a change. Pair it with the exact [Call MCP tool](https://docs.livefaces.ai/workflows/nodes/call-mcp-tool.md) action and inputs the participant is approving.

## Configure

1. Choose **Action to confirm** and describe the intended action in **Instructions**.
2. Bind the same action details as the paired tool.
3. Connect `confirmed` to that tool and `rejected` to a route that does not execute it.
4. Handle `error` and `timeout` without treating either as approval.

On a write tool, **Insert matching confirmation** creates the paired step. Review its details and connections before testing.

## Outcomes

| Outcome | Meaning |
| - | - |
| `confirmed` | The participant approved the described action. |
| `rejected` | The participant declined the action. |
| `error` / `timeout` | Confirmation failed or exceeded its execution limit. |

## Scenario: change a delivery preference

The participant wants an order left at reception. Bind the order reference and proposed delivery preference to both the confirmation and the write tool. Ask:

> Update the delivery preference for this order to leave at reception?

Route `confirmed` to the update tool. Route `rejected` to a message acknowledging that the change was declined, then end or continue to a later support step. If the action details change, confirm the new details before executing the write.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.