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

# App Integrations

Using the underlying iMBrace system, the workflow platform allows users to perform automated tasks on other apps (e.g. Slack, Shopify, CRM software) using the APIs they provide.

In many cases, this requires users to create **API keys** in the respective apps, and create **credentials** in iMBrace to store those API keys. This allows the iMBrace platform to perform tasks on the user's behalf.

Alternatively, **OAuth** can be used to authenticate a user to a service through iMBrace. This allows iMBrace to perform tasks with the same permissions as the user has on the respective apps.

This section provides step-by-step guides to common app integrations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://imbrace.gitbook.io/imbrace-documentation/integrations/app-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.