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

# Trigger Another Workflow

Start another workflow in your organization from this step. Useful for breaking complex automations into smaller, reusable pieces.

Built-in action Built In

Start another workflow in your organization from this step. Useful for breaking complex automations into smaller, reusable pieces.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `trigger-workflow` |
| Category | Built In |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `workflow`, `trigger`, `sub-workflow`, `orchestration`, `automation` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `workflowId` | `string` | Yes | ID of the target workflow to trigger. Must be a published workflow in the same organization \(only published workflows appear in the selector\). |
| `payload` | `object` | No | Optional data to pass to the target workflow. If the target has declared inputs, access them via {{root.input.fieldName}}. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggeredWorkflowId` | `string` | Yes | ID of the triggered workflow |
| `triggeredWorkflowName` | `string` | Yes | Name of the triggered workflow |
| `runStatus` | `string` | Yes | Status of the triggered run |
| `triggeredAt` | `string` | Yes | ISO 8601 timestamp when the workflow was triggered |

## Examples

**Workflow node**

```json
{
  "type": "trigger-workflow",
  "payload": {
    "workflowId": "wf_abc123"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/trigger-workflow/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "workflowId": "wf_abc123"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.