> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows.md).
# Creating & Managing Workflows
Users can create and manage workflows in AccessNow with the **Workflow Builder**.
{% hint style="info" %}
[**Workflow templates**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/working-with-workflow-templates.md) **are the primary way to create and manage workflows.** They support simple form-input changes, such as adding or removing fields, changing field properties, incorporating additional information from Command Centre, and using different labels.
AccessNow workflows are flexible and support many processes. Contact your Gallagher representative for a template when making **major changes or creating a completely new workflow**.
The team is also improving usability so Channel Partners can create and edit workflows independently.
{% endhint %}
With the visual interface, users can design and implement workflows without requiring extensive coding knowledge. It enables businesses to quickly adapt to evolving needs by customizing workflows to align with specific operational requirements.
The section covers creating workflows, including using workflow templates and importing them. It also discusses the elements needed to build and configure workflows.
---
# 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://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows.md?ask=&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.
