> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/shared/integrations.md). # Integrations The Integrations tab connects your app or agent to external services. Every connection you set up here is available to the Riff agent and to your built agent as a credentialed data source or action target — no manual token handling required. Available in both the App builder and Agent builder via the **+** button. ## What you see A searchable grid of integration cards. Each card shows the service name, its logo, and its current connection status. A refresh icon sits at the top right. ## Connecting a service Click any integration card to open a detail panel. From there you can: * **Connect** — for OAuth services, this takes you through the authorisation flow in your browser * **Disconnect** — remove the connection * **Reconfigure** — update connection settings Once connected, the integration is immediately available for the Riff agent to use. ## Account-level integrations (enterprise) Enterprise teams configure shared integrations at account level — for example, a single SAP connection that all apps and agents can use without each team member managing credentials. Click **Link Account Integration** to attach an account-level integration to your project. Once attached, it appears as environment variables in your backend. Team members can use it without seeing the underlying credentials. ## Asking the Riff agent to connect You can also describe what you need in chat: *"Connect this agent to Slack so it can post exception alerts to #procurement."* The Riff agent will guide you through authorising the connection. For ERP connectivity (Infor LN/M3, SAP, Oracle ERP Cloud, Microsoft Dynamics 365), see the [Integrations section](/integrations/about-integrations-v2.md) for per-system setup guides. --- # 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://docs.riff.ai/reference/shared/integrations.md?ask=&goal= ``` `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.