Integration · ERP
AI agents for Coupa
Read Coupa spend data from your instance: invoices, purchase orders, requisitions, suppliers and expense reports, filtered by status, dates or any Coupa field, to answer procurement and accounts payable questions.
- Actions
- 7
- Read
- 7
- Write
- 0
Actions
What your agents can do in Coupa
7 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 7
Look things up. Nothing changes.
List invoices
Lists supplier invoices, newest first by default, optionally filtered by status.
Get an invoice
Reads one invoice by its Coupa ID with its lines, supplier, amounts and taxes, status, approvals, payment terms and attachments list.
List purchase orders
Lists purchase orders, newest first by default, optionally filtered by status (issued, closed, cancelled, buyer_hold …), PO number (filters {"po-number": "1234"}), supplier or dates.
Get a purchase order
Reads one purchase order by its Coupa ID: number, status, supplier, ship-to, lines with quantities, prices and received amounts, totals and dates.
List requisitions
Lists purchase requisitions (requests to buy), newest first by default, optionally filtered by status (draft, pending_approval, approved, ordered …), requester or dates through filters.
List suppliers
Lists suppliers, optionally filtered by status (active, inactive) or by name or number through filters (like {"name[contains]": "Acme"}).
List expense reports
Lists expense reports, newest first by default, optionally filtered by status (draft, pending_approval, approved, paid …), submitter or dates through filters.
Write 0
Create, change or send.
This tool only reads, so nothing in it changes.
Read only
Every action here only reads, so an agent can look things up in Coupa but cannot change anything there.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste the client ID and secret of an app your organization registered with Coupa. The platform fetches its tokens itself (OAuth client credentials).
Settings
- Instance host
- Scopes
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Coupa data
Ask a question in plain words. The agent can list invoices, get an invoice or list purchase orders in Coupa, then answers with what it found.
- 02
Share what it finds in Slack
Give one agent Coupa and Slack: it can list invoices in Coupa and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "List invoices" to a workflow, and it runs in Coupa the same way every time, with or without an agent.
FAQ
Coupa and MyDeepAgents
Can MyDeepAgents connect to Coupa?
Yes. The Coupa connector has 7 actions, all of which only read. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Coupa?
Paste the client ID and secret of an app your organization registered with Coupa. The platform fetches its tokens itself (OAuth client credentials). The connection also asks for: Instance host and Scopes. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Coupa without asking?
No. Every Coupa action only reads, so an agent can look things up there but cannot change anything.
Can I use Coupa in workflows as well as agents?
Yes. Every Coupa action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Coupa to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.