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

# Start process by workspace, app, and process name

> Start a process using the workspace's active build — the simplest public REST entry point for triggering a FlowX process from your own backend or scheduled job.

<Tip>
  Looking for end-to-end guidance on calling FlowX from your own app? See [Consuming FlowX from external apps](/5.9/docs/platform-deep-dive/integrations/consuming-flowx-from-external-apps).
</Tip>

This is the recommended entry point when you want to start a process from outside FlowX (a backend service, a scheduled job, a partner system) and you do not want to manage `buildId` lookups yourself. The runtime resolves the active build for the given `(workspaceId, appId)` pair automatically.

If you need to pin to a specific build, use [Start process by build id and process name](./rest2) instead.

## Path parameters

<Info>
  **Need help finding these IDs?** See the [Finding Identifiers and Parameters](../../platform-deep-dive/integrations/finding-identifiers-and-parameters) guide.
</Info>

<ParamField path="workspaceId" type="string" required example="2ae77b6a-d284-4a0b-ab23-ceaa364c7122">
  The ID of the workspace that owns the application.
</ParamField>

<ParamField path="appId" type="string" required example="dbe0ab87-539b-4015-962d-6e73226b9e58">
  The ID of the application. Must exist in the specified workspace.
</ParamField>

<ParamField path="processName" type="string" required example="customer_onboarding">
  The name of the process definition to start.
</ParamField>

## Request headers

<ParamField header="Authorization" type="string" required>
  Bearer token from the configured identity provider. Format: `Bearer <token>`.
</ParamField>

<ParamField header="Content-Type" type="string" required>
  Must be `application/json`.
</ParamField>

## Request body

A JSON object with the initial process values. The exact shape depends on the process definition.

```json theme={"system"}
{
  "customerEmail": "alice@example.com",
  "loanAmount": 25000
}
```

## Response

Returns the new process instance, including its `uuid` (use this for subsequent calls) and `state`.

```json theme={"system"}
{
  "processDefinitionName": "customer_onboarding",
  "uuid": "24cb4216-83a4-4782-84cb-d702b54b9b7d",
  "state": "STARTED",
  "applicationId": "dbe0ab87-539b-4015-962d-6e73226b9e58",
  "buildId": "7d5560be-3846-49fa-9c17-4059c54c7c5f",
  "instanceMetadata": {
    "processInstanceUuid": "24cb4216-83a4-4782-84cb-d702b54b9b7d"
  }
}
```

<RequestExample>
  ```bash theme={"system"}
  curl -X POST "{BASE_URL}/api/runtime/wks/{workspaceId}/app/{appId}/process-name/{processName}/start" \
    -H "Authorization: Bearer <token>" \
    -H "Content-Type: application/json" \
    -d '{
      "customerEmail": "alice@example.com",
      "loanAmount": 25000
    }'
  ```
</RequestExample>