> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/integrations/workflows.md).

# Workflows

The code that runs on a trigger, a schedule, or an API call.

**Integrations → Workflows** · `/integrations?tab=workflows`

A workflow is JavaScript. One file, `<slug>.js`, exporting one function:

```javascript
export default async function (ctx) {
  // ctx.input, ctx.headers; connectors via fastn.connector.<slug>.<action>()
}
```

There is no node palette and no drag-and-drop step builder. Everything else on this screen configures, describes, tests or deploys that function.

### The list

| Column                     | Notes                                                                                                                                                                                                                                                                          |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| checkbox                   | Selects rows.                                                                                                                                                                                                                                                                  |
| **Workflow**               | Name, slug and description.                                                                                                                                                                                                                                                    |
| **Status**                 | One of `Live`, `Published`, `Paused`, `In review` or `Unpublished` (see below).                                                                                                                                                                                                |
| **Latest**                 | The newest published version, for example `v2`. This is what the test environment runs. A dash means there is no published version yet (tooltip: *No published version yet.*).                                                                                                 |
| one column per environment | Headed by the environment's slug, and shown only when your organization has environments. Each cell shows the version deployed there, for example `v2`, or `v1 · 1 behind` when newer published versions have not been deployed to it. A dash means nothing is deployed there. |
| **Updated**                | Last change.                                                                                                                                                                                                                                                                   |
| actions                    | An **Executions** link to the workflow's runs, **Run** to execute on demand, and a `⋯` menu with **Edit** (or **View** for an inherited workflow) and **Delete**.                                                                                                              |

What each status means:

| Status        | Meaning                                                                                   |
| ------------- | ----------------------------------------------------------------------------------------- |
| `Live`        | A published version is deployed to the default (live) environment.                        |
| `Published`   | Published; the test environment runs it, but it is not deployed to live yet.              |
| `Paused`      | Published, but disabled: calls are refused until it is enabled again.                     |
| `In review`   | A publish is waiting on a GitHub pull request; the version is created when the PR merges. |
| `Unpublished` | Never published.                                                                          |

Two tooltips explain why a call fails, and the first is the string you will search for:

> Never published. Every call returns WORKFLOW\_NOT\_PUBLISHED until a snapshot is published. Draft edits alone do not make a workflow runnable.

> Nothing deployed to \<environment>. A call naming this environment fails until a version is deployed to it.

**Search workflows** filters by name; pills split the list by execution tier: **All**, **Instant**, **Standard**, **Long**.

Two buttons sit top-right: **Connect GitHub**, which connects your organization to a GitHub repository, and **Create workflow**, which gives you an empty one.

### In this section

* [The editor](https://docs.fastn.ai/build/integrations/workflows/the-editor.md)
* [The tabs](https://docs.fastn.ai/build/lifecycle/the-tabs.md)
* [Lifecycle](https://docs.fastn.ai/build/lifecycle.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 by asking a question.

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

```
GET https://docs.fastn.ai/build/integrations/workflows.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 `automate deployments from our CI pipeline` 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.
