Skip to main content



Coupa Success Portal

Coupa Connector for Mulesoft

Latest Coupa Connector Version : 3.0.0 (Released 2021-02-24)
        Mule Runtime Version : 4.1.x
        Anypoint Exchange Link


This connector facilitates the integration with the Coupa’s API, providing a mean to access Coupa web services, you could use Coupa connector within mule flows to send and receive data using the Coupa API.

It provides access to Addresses, Approvals, Expense Report, Inventory Transactions, Invoices, Lookup Values, Purchase Orders, Requisitions, Suppliers, Users, Charges, CoupaPay Payments, Contracts, Items, Supplier Items.

Read through this user guide to understand how to set up and configure a basic flow using the connector. Track feature additions, compatibility, limitations and API version updates with each release of the connector using the Connector Release notes attached below. Review the connector operations and functionality using the demo appliccation attached below.

MuleSoft maintains this connector under the Certified support policy.


This document assumes that you are familiar with Mule, Anypoint StudioAnypoint Core Components and Mule Flow Design Center.

Hardware and Software Requirements

For hardware and software requirements, please visit the Hardware and Software Requirements page.


Software Version

Mule Runtime

4.1.x and higher

Installing the Connector

You can install the connector in Anypoint Studio using the instructions in Installing a Connector from Anypoint Exchange.

Configuring the Connector Global Element

To use the Coupa connector in your Mule application, you must configure a global Coupa element that can be used by the Coupa connector. The Coupa connector offers the following global configuration(s), requiring the following credentials: Coupa API Key and Instance:

Field Description

Coupa API key

Enter the API Key retrieved from your Coupa admin or Integration Architect for generating and providing the key to you.


Each Coupa customer has their own url, of the form



Using the Connector

Connector Namespace and Schema

When designing your application in Studio, the act of dragging the connector from the palette onto the Anypoint Studio canvas should automatically populate the XML code with the connector namespace and schema location.


If you are manually coding the Mule application in Studio’s XML editor or other text editor, define the namespace and schema location in the header of your Configuration XML, inside the <mule> tag.
<mule xmlns:coupa="" xmlns=""
	xmlns:xsi="" xsi:schemaLocation="">
	  <!-- put your global configuration elements and flows here -->


Inside the <version> tags, put the desired version number, the word RELEASE for the latest release, or SNAPSHOT for the latest available version. The available versions to date are:

  • 3.0.0

Demo Mule Applications Using Connector

Existing demo demonstrate how to use the connector for:

Example Use Case

The following example shows how to get an invoice using the connector:

Get an invoice

  • In Anypoint Studio, click File > New > Mule Project, name the project, and click OK.

  • In the Mule Palette, click on the "HTTP" group and select the Listener component. Now drag and drop it into the flow designer.

  • First, we need to create a configuration for the HTTP listener before using it. Click on the HTTP listener and add new configuration by pressing the green plus icon.

  • Leave the defaults and click OK.

  • Set the value to "show-invoice".


  • In the Mule Palette, click on the "Coupa" group and drag and drop Get into the flow designer, then create a new configuration and set your API Key and the instance URL.

  • In the Coupa General section, for Object type pick Invoice (invoice) and put 1 (or any valid invoice id) in the ID field.



After an object type is selected, the output metadata view is getting generated based on the pick

Error handling

The connector might generate a different type of errors while using it in flows. It is good to configure separate strategy for every error type using the Error Handling components.

Coupa Errors:





Configuring custom fields

Custom fields can be added on top of the basic datasense fields. Available data types for custom fields are StringDateDate_TimeIntegerDoubleFloatLongDecimalBoolean and Reference.

Example configuration:

some-custom-field,String; other-custom-field,Date_Time; custom-reference-field,Reference:user

Custom fields can be add in the Custom Metadata tab of the Coupa Global Configuration.


API Resources

Coupa Connector Release Notes


Support Resources