> 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/archive/integrations-legacy-saas-connectors/native-integrations.md).
# Native Integrations
Get going in minutes. OAuth in. Ship.
####
### How it works
Two ways to add integrations:
1. **Let the agent drive.** If a task needs an integration, the agent prompts you to connect. Approve once. Done.
2. **Add proactively.** Click **+ More → Integrations** and pick a provider.
After connect, the agent:
* Checks scopes (keep them tight).
* Runs a quick test (e.g., “Create Sheet,” “List Deals”).
* Uses the integration in the build plan and tasks — no manual wiring.
#### Typical flows
* Ingest a **CSV** → write rows to **Google Sheets**.
* Charge a card with **Stripe Checkout**; store receipts in **Database**.
* Pull **HubSpot** contacts → enrich → push updates back.
* Turn **Notion** pages into tasks; sync status both ways.
> Coverage grows. If you don’t see your tool, use a Custom API or ask the agent to add it.
---
# 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.riff.ai/archive/integrations-legacy-saas-connectors/native-integrations.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.
