Deep Dive: Coupa Connector

Document created by rodrigo.delatorre Employee on May 3, 2018Last modified by Adam Arrowsmith on May 7, 2018
Version 14Show Document
  • View in full screen mode

In this deep dive, we'll look at the Coupa connector to see how to configure it to work on the Boomi AtomSphere platform and then how to use it to create a requisition in Coupa.




The Coupa connector enables you to move data into and out of Coupa and integrate any on-premise applications and legacy systems with Coupa. You can use this connector and integrate Coupa with other On Demand or SaaS-based applications such as Intacct, Salesforce, SmartTurn, etc.


 Get the example process used below from the Process Library here.



Configure Coupa

The Coupa connection represents a single Coupa organization including login credentials. If you have multiple organizations, you need a separate connection for each.


Configure the Connection component

Follow these steps to configure the connection component for the Coupa connector within AtomSphere.


  • In the Connection tab, set the URL field as: https://<companyName>
  • Enter your password in the Token field


Refer to this article in the Boomi help documentation for details on how to generate a Coupa Security token.

Note that the Test Connection button was added. This will give you the possibility to test the recently established connection before start creating processes.


Integrate Boomi with Coupa

Now that we’ve completed the setup, let’s build a process that uses it. The following processes use the Coupa connector to create a new requisition in Coupa and then approve that requisition.


Create a requisition

This first part of this process creates a requisition using a Message shape to pass a requisition request xml document.


Requisition request XML Example:


Note that the Id’s provided must exist in your Coupa Instance.


While configuring the operation, during Import, you will be able to select the object type to create, in this case, Requisitions. This will generate the needed profiles in order to proceed with operation.



Note that the option “Return Object” is set to “all”, which imply that the full object is returned. The other options will shorten the response, in the case of “limited”, only the Id of the recently created Requisition will be provided. If “none” is selected, no output document is obtained.


Validate if the requisition was created

This second part of the process validates if the requisition was created successfully. This could be done in several ways, for example checking that, in the Create Requisition response profile, the Requisition Id was included, or, as we did in our example process, check that the status message of the operation is “Created”.




Execute Approval of the Requisition

In the third part of the process we execute the approval of the recently created Requisition (This was created intentionally as “Pending Approval”).



While configuring the Execute operation and during Import, the Object type “Approve Approval” must be selected.



As a parameter of the operation, the Approval Id must be entered. This can be found in the Output Document from the Create Requisition operation.



To validate that the operation was properly executed, we are going to check, with a decision shape, that the Approval status was updated to approved in the response profile.




In this simple process we have seen how the Coupa connector can be used to create a Requisition and take additional action on the newly created Requisition, in this case Approve the approval created with it.