# Business actions inside workflows

> Map data into connected actions, wait for the result and reuse a published child flow.

Canonical: https://valuechat.app/docs/workflow-external-actions
Category: Workflows

## Before you start

Use a test channel or sample conversation first. Confirm the result before applying the setup to production traffic.

## How it works

1. Choose a connection. Add an App/MCP or supported integration node, select an enabled workspace connection and one of its allowed actions. Configure the arguments from literals, contact/message values or previous step outputs.

2. Order of execution. The event commits before remote work begins. Later nodes run after the actual external response. A message-confirmation node must not run as if a failed or unknown action succeeded.

3. Reuse. Call an On demand child workflow from an event flow or an agent. Workspace/channel checks and cycle protection still apply; a child workflow does not bypass its connection permissions.

4. Recovery. Saved executions, per-node receipts and ownership checks prevent ordinary replay of completed writes. If a request may have reached the provider but the result is unknown, inspect the external system before retrying.

5. Partial effects. If step one writes a sheet and step two fails, the first external change can remain. Execution history explains which steps completed; no cross-provider atomic rollback is promised.

## What to verify

- The expected channel, conversation, contact or execution is visible.
- The assignment matches the configured routing.
- No customer-facing message claims an action that failed.
- Activity or execution history explains the result.

## Need help?

support@valuechat.app. Never send API keys or passwords.