Skip to content
Integrating with Coupa › Integrating with external procurement applications › Procurement › Asset Management common applications › IT Service Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Create a Coupa integration profile

Create a Coupa integration profile to verify the status of the procurement-scheduled jobs, entitlements, and entitlement import errors created through this profile.

Before you begin

Role required: sam_admin

Create an OAuth 2.0 connection with Coupa to get the Client ID and Client Secret. For more information, see OAuth 2.0 Getting Started with Coupa API. Save the Client ID and Client Secret in a secure location for later use.

You must set the following scopes while creating an OAuth 2.0 connection with Coupa.

  • core.approval.configuration.read
  • core.approval.read
  • core.approval.write
  • core.catalog.read
  • core.common.read
  • core.contract.read
  • core.contract.write
  • core.inventory.adjustment.read
  • core.inventory.adjustment.write
  • core.inventory.asn.read
  • core.inventory.common.write
  • core.inventory.consumption.read
  • core.inventory.consumption.write
  • core.inventory.receiving.read
  • core.inventory.receiving.write
  • core.inventory.return_to_supplier.read
  • core.inventory.transfer.read
  • core.inventory.transfer.write
  • core.invoice.delete
  • core.invoice.read
  • core.invoice.write
  • core.item.read
  • core.item.write
  • core.legal_entity.read
  • core.purchase_order.read
  • core.purchase_order.write
  • core.requisition.read
  • core.requisition.write
  • core.sourcing.pending_supplier.read
  • core.sourcing.pending_supplier.write
  • core.sourcing.read
  • core.sourcing.response.award.write
  • core.sourcing.response.read
  • core.sourcing.response.write
  • core.sourcing.write
  • core.supplier.read
  • core.supplier.write
  • core.user.read
  • core.user.write

Note: If these scopes aren't associated with the Client ID and Client Secret, the OAuth token flow fails on ServiceNow.

Procedure

  1. Navigate to Software Asset Workspace > License operations > Purchasing > Procurement integrations.

  2. Select New.

  3. On the form, fill in the fields.

FieldDescription
Display nameName of the procurement integration profile. For example, `Coupa integration`.
Connection & CredentialsConnection and credential alias for Coupa. This field gets automatically populated to sn_coupa_spoke.Coupa_OAuth.
Profile typeType of integration profile. Select Coupa integration.
StatusStatus of the integration profile. - If you haven’t published the integration profile, this field is automatically set to Draft. - If you’ve already published the integration profile, this field is automatically set to Published.
ActiveThis field is visible and set to true only when the integration profile is published. If you set this field to false, the associated requisitions with this integration profile aren’t created and tracked.

  1. Select Save.

  2. Select the Preview icon

Image omitted: preview-icon.png
Preview icon next to the Connection & Credentials field.
You get redirected to the Connection & Credential Aliases form.

  1. Select Create New Connection & Credential in the Related Links section to create connection credential.

  2. In the dialog box, fill in the fields.

  1. Select Create and Get OAuth Token.

    Your ServiceNow instance creates an OAuth for Coupa and then automatically returns you to the Integration Profile form.

  2. Create a child alias that can uniquely identify the connection and credentials for this integration profile.

    The first Coupa integration profile that you create uses the default (parent) connection and credential alias for Coupa. Each additional Coupa integration profile that you create needs a unique child alias that helps differentiate the connection and credentials between each integration profile.

    1. On the Connection & Credential Aliases form, select the link under Child Aliases > Parentalias=*** to add child aliases.

    2. Select New.

    3. Enter a name for the child alias in the Name field.

    4. Right-click the form header and then select Save.

    5. After the form reloads, select the Create New Connection & Credential related link.

    6. Repeat steps 7 and 8.

    7. In the Connection & Credential field of the Integration Profile form, select the lookup icon to locate and select the child alias that you created.

      Selecting the child alias associates the alias with the integration profile. Your ServiceNow instance uses this alias to identify the connection and credentials for this integration profile.

  3. Select Publish.

Result

After you publish the integration profile, the scheduled job ITAM - Sync Coupa purchase orders runs daily and fetches the status of the already created requisitions.

Note: If you haven't created any requisition, the scheduled job doesn't run.

You can view this information by clicking the Procurement Integration Jobs tab.

What to do next

Verify if the scheduled job ITAM - Sync Coupa purchase orders has run successfully by selecting the Integration Scheduled Job Results tab. If the job has failed, you can view the list of errors by following these steps:

  1. On the Procurement integration profile form, select the Procurement Integration Job Log related list.
  2. Open the job log record where the displayed status shows as failed.
  3. Select the related list Asset Job Log Details to find out the reason for the job failure.

Create software requisitions directly on Coupa through the ServiceNow Procurement application to purchase software.

If you want to delete the Coupa integration profile, see Deleting an external procurement application integration profile.

sndocs is an independent community mirror and is not affiliated with or endorsed by ServiceNow.

ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc., in the United States and/or other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

© 2026 ServiceNow, Inc. All rights reserved.

Documentation content is redistributed under the Apache License 2.0 from the ServiceNowDocs repository.

FieldDescription
Name \(Connection\)Name to identify the connection uniquely. For example, `Coupa OAuth connnection`.
Connection URLURL to make a connection to Coupa. Use the `https://` format.- For customer instances, use the `https://{organization_name}.coupahost.com` format. - For partner and demo instances, use the `https://{organization_name}.coupacloud.com` format.
Name \(Credential\)Name to identify the credential uniquely. For example, `Coupa OAuth credential`.
Token URLURL used to generate OAuth token. Use the `https:///oauth2/token` format.
OAuth Client IDIdentifier \(Client ID\) generated in Coupa.
OAuth Client SecretSecret \(Client Secret\) generated in Coupa.