Resources · Make integration

Coupa Make integrationAutomate Coupa with Make.

Can Make move a Coupa requisition forward without anyone opening Coupa? The Coupa Make integration gives you 5 modules: 4 actions and 1 search, all about approvals and requisition lines. This page shows procurement and finance ops teams how to connect Coupa and build a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Coupa integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Coupa Make integration do for you?

The Coupa Make integration lets Make act on your requisitions for you: it grants or rejects an approval, updates a requisition line and adds an approver. You build a scenario in Make (the automation, a chain of modules) and each module (one brick of that chain) does one of these jobs in Coupa.

Approvals decided outside Coupa. A manager answers a request in a chat or a form tool, and the scenario turns that answer into Grant an Approval or Reject an Approval. The decision lands in Coupa without a second login.

Requisition lines kept in sync. When a request changes in the tool where your team plans purchases, Update a Requisition Line writes the change to the matching line, so the buyer works from the current version.

The right approver, added on cue. Some requests need an extra signature, say above a budget threshold you define in the scenario. Add an Approver to a Requisition puts that person on the chain.

Two limits to know before you start. Coupa has no trigger module in Make, so the scenario starts from another app or from the Make schedule. And the Coupa app is reserved to the Make Enterprise plan; the Make pricing page lays out the plans. Anything the 5 modules skip goes through Make an API Call.

If you are still weighing tools, the n8n vs Make comparison puts both side by side, and the Make training covers scenario building from zero.

Connect

How do you connect Coupa to Make?

  1. 01

    Create an OAuth client in Coupa

    Log in to Coupa and open Setup > Integration > OAuth2/OpenID Connect Clients, then click Create. Set Grant Type to Client credentials, fill in the name, login and contact details, paste https://www.make.com/oauth/cb/coupa in JWK URI, tick the required scopes and click Save.

  2. 02

    Copy the Identifier and the Secret

    On the client you just saved, copy the Identifier value. Click Show/hide next to the Secret field and copy that value too. Keep both somewhere safe: they are the two credentials Make asks for in the next step.

  3. 03

    Add the connection in Make

    In any Coupa module, click Create a connection and pick Coupa as the connection type. Name it, type your account address in Resource URL without https://, paste the Identifier and Secret, select the scopes and click Save. That connection is then reused by every Coupa module.

First scenario

Your first scenario with Coupa and Make

GoalWhen a request is updated in the app your team plans purchases in, Make updates the matching Coupa requisition line and adds the approver it needs.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module is the other app, the one where your requests change, since Coupa has no trigger of its own.

  2. 02

    Add Update a Requisition Line

    Click the + on the right of the first module, search for Coupa and pick Update a Requisition Line. Select your Coupa connection, then map the values from the first module into the line fields.

  3. 03

    Add the approver

    Click the next + and choose Add an Approver to a Requisition. Map the requisition and the approver from the earlier modules, so each bundle (one request passing through) gets the right person.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that the line and the approver match in Coupa.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule: every 15 minutes by default, 1 minute at the lowest on paid plans. Then switch the scenario on, and each module run counts as one operation on your plan.

Modules

What the Coupa modules do in Make

Coupa gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Coupa1

Grant an Approval

Action

In Make“Grants a requisition approval.”

Approves a pending requisition approval in Coupa, so the approver records a decision without opening Coupa.

When to use it
a manager says yes in the tool your team already uses, and that yes should count in Coupa right away.
Watch out
an approval granted by the scenario is a real decision, so keep a condition before this module that only lets confirmed answers through.
Coupa2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Coupa API with the connection you already set up, which covers everything the four other actions and the search leave out.

When to use it
you need a Coupa object or an operation that none of the listed modules offers.
Watch out
the request is yours to write, and the OAuth client only reaches what its scopes allow, so add a scope in Coupa first if a call is refused.
Coupa3

Reject an Approval

Action

In Make“Rejects a requisition approval.”

Turns a pending requisition approval into a rejection, so a declined request gets a clear answer in Coupa instead of an open approval.

When to use it
the budget owner declines in a chat or a form, and Coupa should reflect that decision instead of waiting.
Watch out
if Grant an Approval sits in the same scenario, keep the two paths apart so one answer never reaches both modules on the same approval.
Coupa4

Update a Requisition Line

Action

In Make“Updates a requisition line.”

Changes an existing line on a Coupa requisition, so the buyer and the approvers see the latest numbers rather than the first draft.

When to use it
a request is corrected in the planning sheet or the project tool upstream of Coupa.
Watch out
it edits one line per bundle; a request with several lines needs one bundle for each line coming from the earlier module.
Coupa5

Add an Approver to a Requisition

Search

In Make“Adds an approver to a requisition.”

Puts an extra person on the approval chain of a requisition, which is how a scenario brings in a finance lead or a department head only when a request calls for it.

When to use it
a rule you set in the scenario, such as an amount or a category, means someone else has to sign.
Watch out
Make files it as a search, and a search can return zero, one or several bundles, so check what it sends to the next module.
Need help

Need help automating Coupa with Make?

A person reads every message.

FAQ

Coupa and Make: common questions

01Is the Coupa Make integration free?
No. The Coupa app is an enterprise app, and Make reserves enterprise apps to its Enterprise plan. The Free plan gives you 2 active scenarios, a 15 minute minimum between scheduled runs and files up to 5 MB, and it includes the 3,000+ standard apps, but Coupa is not one of them. Paid plans are Core, Pro, Teams and Enterprise, with usage counted in credits, that is operations, each month. Only the Enterprise tier unlocks the 5 Coupa modules, so check your Make plan before you plan the build.
02What do you need to connect Coupa to Make?
You need a Coupa account that can open Setup and create an OAuth2/OpenID Connect client, plus a Make organization on the Enterprise plan. In Coupa, the client uses the Client credentials grant type, the Make redirect address in JWK URI and the mandatory scopes, among them core.accounting.read. You then copy the Identifier and the Secret. In Make, you fill in the connection name, your Resource URL without https:// and those two values. The old API key method no longer works, since Coupa has deprecated it.
03Does the Coupa Make integration have a trigger?
No. The 5 Coupa modules are 4 actions and 1 search, so nothing inside Coupa can start a scenario on its own. You start it another way. Either the first module belongs to another app, a form or a chat for example, and its trigger launches the run. Or you put the scenario on a schedule, which Make sets to every 15 minutes by default and lowers to 1 minute on paid plans. After that, the Coupa modules act on the requisitions that the first module hands over.
04What if the Coupa module you need is missing?
Use Make an API Call. It sends any request to the Coupa API with the same connection as the other modules, so you are not limited to granting, rejecting, updating a line and adding an approver. The catch is that you write the request yourself, and the call only reaches what the OAuth client scopes allow. If Coupa refuses a call, open the client in Coupa, add the scope and save. The Make troubleshooting page on this site helps when a scenario fails for another reason.
05Should you use Make or n8n for Coupa?
It depends on what your team already runs. On Make, Coupa comes as 5 ready modules centered on requisition approvals, plus Make an API Call for the rest, and it needs the Enterprise plan. The same app often has an n8n node too, so check whether one exists for Coupa and compare the operations each side covers against your approval flow. Pick the tool your team can maintain, and base the choice on the modules you actually need rather than on the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations