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

# Native Integrations

Connect Riff to the systems your team already lives in. Set credentials once — your apps and agents handle the rest.

### ERP Connectors

<table 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>Infor LN / M3</strong></td><td>Purchase orders, goods receipts, vendor master, invoice data. REST API + ION API Gateway.</td><td><a href="https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/infor-ln/README.md">https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/infor-ln/README.md</a></td></tr><tr><td align="center"><strong>SAP S/4HANA</strong></td><td>Purchase orders, materials, invoices, cost centres. OAuth 2.0 / service key.</td><td><a href="https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/sap/README.md">https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/sap/README.md</a></td></tr><tr><td align="center"><strong>Oracle ERP Cloud</strong></td><td>PO lines, receipt transactions, supplier data, AP invoices. OAuth 2.0.</td><td><a href="https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/oracle-erp/README.md">https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/oracle-erp/README.md</a></td></tr><tr><td align="center"><strong>Microsoft Dynamics 365</strong></td><td>Purchase orders, vendor invoices, inventory, cost centres. Azure AD OAuth.</td><td><a href="https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/dynamics-365/README.md">https://github.com/ElleNealAI/riff-docs/blob/main/integrations/native-integrations/dynamics-365/README.md</a></td></tr></tbody></table>

### Communication & Productivity

<table data-view="cards"><thead><tr><th align="center"></th><th></th></tr></thead><tbody><tr><td align="center"><strong>Microsoft Outlook</strong></td><td>Send supplier confirmations, delivery alerts, and exception notifications directly from your agents.</td></tr><tr><td align="center"><strong>Slack</strong></td><td>Post procurement exception digests, approval requests, and delivery alerts to your team channels.</td></tr><tr><td align="center"><strong>Microsoft SharePoint</strong></td><td>Read supplier contracts, PO documents, and specification files. Write exception reports and reconciliation outputs.</td></tr></tbody></table>

### How it works

Two ways to connect:

1. **Let the agent drive.** When a task needs an integration, the agent prompts you to connect. Provide credentials once. Done.
2. **Add it yourself.** Open **Integrations** in your app or agent workspace, pick a connector, and follow the setup steps.

After connecting, your agent:

* Reads live data from the source — no manual exports needed
* Takes action: logs confirmations, updates statuses, flags exceptions — with a full audit trail
* Escalates to your team when it needs a decision it can't make itself

#### Typical procurement flows

* Pull overdue POs from **Infor LN** → chase supplier via **Outlook** → log confirmation back to ERP
* Read pending invoices from **SAP** → match against goods receipts → flag mismatches to buyer via **Slack**
* Monitor delivery exceptions in **Oracle ERP Cloud** → build a daily exception dashboard → push digest to procurement manager
* Reconcile vendor invoices in **Dynamics 365** → approve matched lines → escalate disputes to AP team

> Coverage grows. If your ERP or tool isn't listed, use a [Custom Integration](/archive/integrations-legacy-saas-connectors/custom-integrations.md) or ask your agent to wire it up.


---

# 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/integrations/native-integrations-v2.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.