> 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/integrations/about-integrations-v2.md).

# About Integrations

Riff is built to run on the systems your procurement and operations teams already depend on. Connect to your ERP first — then add the communication tools, document stores, and data pipelines your business uses every day.

### Two connection types

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>ERP &#x26; Native Connectors</strong></td><td>Pre-configured connectors for the ERPs and productivity tools your teams use daily. Set credentials once. Your apps and agents read live data and take action.</td><td><a href="/pages/zZA4T7Qfol8uJhoowM2i">/pages/zZA4T7Qfol8uJhoowM2i</a></td></tr><tr><td align="center"><strong>Custom APIs</strong></td><td>Connect to any external service — freight carriers, supplier portals, compliance databases, EDI systems — using their REST API. Riff stores credentials securely and handles the wiring.</td><td><a href="/pages/k7liwGOIQ2MS6LwrrBUs">/pages/k7liwGOIQ2MS6LwrrBUs</a></td></tr></tbody></table>

### Start with your ERP

Your ERP holds the data your agents act on: purchase orders, goods receipts, vendor records, invoice lines, cost centres. Connect it first.

| ERP                        | What your apps and agents can read                                              |
| -------------------------- | ------------------------------------------------------------------------------- |
| **Infor LN / M3**          | Purchase orders, goods receipts, vendor master, invoice data, production orders |
| **SAP S/4HANA**            | Purchase orders, materials, invoices, cost centres, goods movements             |
| **Oracle ERP Cloud**       | PO lines, receipt transactions, supplier records, AP invoices, payment terms    |
| **Microsoft Dynamics 365** | Purchase orders, vendor invoices, inventory transactions, cost centres          |

> **No ERP API access yet?** Start with the Custom Integration path — your agent can work with CSV exports, SharePoint files, or Outlook-forwarded confirmations while your IT team sets up the API connection.

### What connecting an integration unlocks

* **Apps** — build dashboards, approval queues, and supplier portals on live ERP data. No manual exports or copy-paste.
* **Agents** — give your agent read and write access so it can chase supplier confirmations, match invoices, and log exceptions back into the ERP automatically.

{% hint style="info" %}
**What's an API?** A deal between systems. Your agent sends a request. The ERP returns data or confirms an action. Every call is logged — full audit trail, reversible actions.
{% 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 dynamically by asking a question.

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

```
GET https://docs.riff.ai/integrations/about-integrations-v2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.