> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/workflow-builder/accessing-the-workflow-builder.md).

# Accessing the Workflow Builder

How to access the workflow builder

{% hint style="warning" %}
Please contact your First Resonance representative or <support@firstresonance.io> if you would like express interest in building automations for your organization.
{% endhint %}

[Navigate](https://staging.firstresonance.io/workflow-builder) to the **Workflow Builder** page designated by the icon that displays connected blocks in the bottom lefthand corner of your screen.

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fgit-blob-e6ef69d58c84a8c36232c3d8c7779dd5a0d8a2ca%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Workflow Builder** icon will not be visible if your company does not have the feature flag enabled. In addition, only users who have the `ReadEmbeddedWorkflowBuilder` permission will be able to see the Workflow Builder icon.


---

# 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://manual.firstresonance.io/workflow-builder/accessing-the-workflow-builder.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.