> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/approval.md).
# Approval
Add manual approval steps into your automations with the ZBrain Approval component to ensure human oversight on critical tasks.
Approval in ZBrain Flow is a workflow tool for managing approvals and permissions. It allows users to create approval requests, generate approval links, and pause flows until a decision is made, ensuring seamless process control and authorization handling.
**How to Integrate Approval with ZBrain Flow**
1. **Click the “+” button in the Flow**: Open your ZBrain Flow and click the plus sign to add a new step.
2. **Search for “Approval”**: Type “Approval” in the search bar to see the available approval-related actions.
3. **Choose the Desired Task**: Select the approval function that fits your workflow requirements.
**Tasks You Can Perform with Approval**
* **Wait for Approval**: Pauses the workflow and waits for a user to approve or reject a request before proceeding.
* **Create Approval Links**: Generates approval links that can be shared externally without pausing the flow, allowing for asynchronous decision-making.
#### **Wait for Approval**
Pauses the workflow and waits for a user to approve or reject a request before proceeding.
#### **How to Configure Wait for Approval** **in ZBrain Flow?**
1. **Add the Step**
* In your ZBrain Flow, click the **+** button to add a new step.
* Search for **“Approval”** and select **Wait for Approval** from the available options.
2. **Place in the Workflow**
* Position the **Wait for Approval** step at the point in your flow where you need to pause execution until a decision is made.
3. **Save and Activate**
* Since there are no additional parameters to configure, save your flow.
* When the flow runs and reaches this step, it will pause until an approval action is taken.
4. **Approval Process**
* Once triggered, an approval request is generated. The flow will remain on hold until someone approves or rejects the request.
* After a decision is made, the flow resumes automatically.
#### **Create Approval Links**
Generates approval links that can be shared externally without pausing the flow, allowing for asynchronous decision-making.
#### **How to Configure Create Approval Links** **in ZBrain Flow?**
1. **Add the Step**
* In your ZBrain Flow, click the **+** button to add a new step.
* Search for **“Approval”** and select **Create Approval Links** from the available options.
2. **Place in the Workflow**
* Position the **Create Approval Links** step at the point in your flow where you need to generate approval links for external or asynchronous decision-making.
3. **Save and Activate**
* Since there are no additional parameters to configure, save your flow.
* When the flow runs and reaches this step, it will generate unique approval links that can be shared as needed.
4. **Approval Process**
* Recipients can click the shared approval links to approve or reject the request.
* Unlike a direct wait step, the flow will continue without pausing, allowing decision-makers to act conveniently.
---
# 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.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/approval.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.