> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/install-and-configure-apps/oauth-2.0-setup.md).

# OAuth 2.0 setup

Some apps require an OAuth 2.0 connection to function on your instance. For example, Slack and Google Sheets need OAuth 2.0 credentials to access the relevant APIs. OAuth 2.0 configuration requires the following:

* A **Client ID** and **Client Secret** from the third-party app you want on your instance. In most cases, you need a developer account with the third party to get the required credentials.
* A **redirect URI**. You can find the appropriate redirect URI at **Administration > Native apps > {app} > Connection in the Account parameters** section. The general pattern for redirect URIs is: `https://{yoursubdomain}.integromat.celonis.com/oauth/cb/{app_name}`
* Enabled third-party scopes. Each module requires specific scopes to access the third-party app.

{% hint style="info" %}
There may be multiple versions of an app if there are multiple API versions. You can add any number of versions as you want.
{% endhint %}


---

# 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://developers.make.com/white-label-documentation/install-and-configure-apps/oauth-2.0-setup.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.
