> 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/workflow-configuration/steps.md). # Steps Steps are the stages of the workflow. Each step represents a specific action or decision point, such as collecting information, performing a check, or sending a notification. Steps break the process into manageable chunks, making it easier for users to follow and for the system to automate checks and actions. ## **Step Types** Available step types for constructing a workflow: * [**Data Setup**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/data-initialisation-step.md)**:** Is used to initialise the Fields when using the AccessNow workflow templates. * [**Input**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/input-step.md): Enables the creation of a form to gather user information, such as entering request details. * [**Process**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/process-step.md): Automatically runs a backend service or performs checks, such as e.g., verifying a cardholder or creating a credential in the Command Centre. * [**Process Task**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/process-task-step.md): Used to to create decision points like e.g. Approvals. * [**End Process**](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/end-process-step.md): Marks the end of the workflow, summarising the outcome. **Example of the Use of Steps in a Workflow** * **Step1 – Input:** Collect user and request details * **Step 2 – Process:** Find Cardholder Record in Command Centre. The process step calls a backend service to look up the cardholder using the email address. * **Step 3 - Process Task:** Initiate an approval task to review and either approve or deny the request. * **Step 4a – Process** After approval, provision access/credentials in Command Centre. Send an approval email notification to the requester. * **Step 4b – Process:** Aftre request denide send a denial notification to the requester. * **Step 5 – EndProcess:** End the workflow. --- # 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/workflow-configuration/steps.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.