> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/bap/business-automation-portal.md).

# Business Automation Portal

A no-code portal for running and managing integrations.

Business Automation Portal is a no-code interface for business users to run and manage integrations.

This portal lets non-developers, including ISVs and SaaS partners, use integrations without coding. It supports self-service execution and white-labeling for embedding in other solutions. Users can launch predefined Processes and monitor their performance.

To get started with Business Automation Portal, contact Frends Sales.

Check out our Business Automation Portal demo here to get started:

{% @storylane/embed subdomain="app" url="<https://app.storylane.io/share/vxzdtwukutlw>" linkValue="vxzdtwukutlw" %}


---

# 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.frends.com/bap/business-automation-portal.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.
