> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/developers/start-workflow.md).

# Start a workflow from your server

Use this endpoint for a published, enabled workflow with the **API call** trigger.

```http
POST /api/v1/triggers/WORKFLOW_ID?account_id=WORKSPACE_ID
Authorization: Bearer YOUR_DISTRO_API_TOKEN
Content-Type: application/json
Idempotency-Key: demo-request-000123
```

```json
{
  "input": {
    "email": "alex@example.com",
    "name": "Alex Example"
  },
  "attribution": {
    "utm_source": "website"
  }
}
```

The `input` keys must match your published trigger schema. The example is not a mandatory schema for all workflows. Attribution is optional.

Required scope: `visual_workflows:start`. The member and token must have access to the explicit workspace.

## Accepted response

A new event returns HTTP 201:

```json
{
  "event_id": "example-event-id",
  "run_id": 789,
  "duplicate": false
}
```

Store the returned run ID. Acceptance does not mean the workflow has finished or a meeting is booked.

## Retry the same event

Reuse the same idempotency key and unchanged input/attribution when a response is lost. A repeated accepted event returns HTTP 200 with `duplicate: true` and the original run information.

Send a key of 1–200 letters, digits, underscores, periods, colons or hyphens. You can also send `idempotency_key` in the body; the header takes precedence.

Reusing a key with different event data returns HTTP 409. Use a new key for a genuinely new event.

See [Read workflow progress](/developers/workflow-progress.md) and [Errors and retries](/developers/errors.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/developers/start-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.