Configure Coupa as your data pipeline source

Set up Coupa as a data pipeline source to extract and sync records into your destination. This guide includes connection setup, pipeline configuration, and key behavior for working with Coupa as a source.

Features supported

The following features are supported when using Coupa as a data pipeline source:

• Extract data using the Coupa REST API
• Support for full and incremental sync
• Field-level selection for object extraction
• Schema drift detection and handling
• Field-level data masking

Prerequisites

You must have the following configuration and access:

• A Coupa instance with API access enabled
• Coupa instance URL
• Required scopes for the API
• Read access to the objects you plan to sync

How to connect

Complete the following steps to connect to Coupa as a data pipeline source. This connection allows the pipeline to extract and sync data from your Coupa instance:

1

Select Create > Connection.

2

Search for and select Coupa on the New connection page.

3

Enter a name in the Connection name field.

Coupa connection setup

4

Use the Location drop-down to select the project where you plan to store the connection.

5

Use the Authentication type drop-down menu to select one of the following authentication types:

• API key
• Client credentials
• Authorization code grant

The required fields vary depending on the authentication type.

6

Fill in the following fields based on the selected authentication method:

1

Enter your Coupa instance URL in the Host field. For example:your-instance-name.coupacloud.com.

2

Enter the API key. You can generate it in Coupa from Setup > Integrations > API Keys.

1

Enter the Client ID of your Open Connect client.

2

Enter the Client secret of your Open Connect client.

3

Enter your Coupa instance URL in the Host field.

4

Select the required Scopes. The core.common.read scope is selected by default.

1

Enter the Client ID of your Open Connect client.

2

Enter the Client secret of your Open Connect client.

3

Enter your Coupa instance URL in the Host field.

4

Select the required Scopes. The core.common.read and offline_access scopes are selected by default.

7

Click Connect to verify and establish the connection.

Configure the pipeline

Complete the following steps to configure Coupa as your data pipeline source:

1

Select Create > Data pipeline.

2

Provide a Name for the data pipeline.

Data pipeline setup

3

Use the Location drop-down menu to select the project where you plan to store the data pipeline.

4

Select Start building.

5

Click the Extract new/updated records from source app trigger. This trigger defines how the pipeline retrieves data from the source application.

Configure the Extract new/updated records from source app trigger

6

Select Coupa from Your Connected Source Apps.

7

Choose the Coupa connection you plan to use for this pipeline. Alternatively, click + New connection to create a new connection.

Choose a Coupa connection

8

Click Add object to open the object wizard.

Add objects

9

Search or browse the list of available Coupa objects. Select the objects you plan to sync and click Add.

Select objects

10

Review and customize the schema for each selected object. When you select an object, the pipeline automatically fetches its schema to ensure the destination matches the source.

Expand object

Expand any object to view its fields. Keep all fields selected to extract all available data, or deselect specific fields to exclude them from data extraction and schema replication.

11

Optional. Configure field-level data protection. After you expand an object, choose how to handle each field:

• Replicate as is (default): Data values at the source are replicated identically to the destination.
• Hash: Hash sensitive data values in the column before syncing to your destination.

Configure field-level data protection

12

Click Add object again to add more objects using the same flow. You can repeat this step to include multiple Coupa objects in your pipeline.

13

Choose how to handle schema changes:

• Select Auto-sync new fields to detect and apply schema changes automatically.
• Select Block new fields to manage schema changes manually. This option may cause the destination to fall out of sync if the source schema updates.

Unsynchronized schema changes, also known as schema drift, can cause issues if not managed. Refer to the Schema drift section for more information.

14

Configure how often the pipeline syncs data from the source to the destination in the Frequency field. Choose either a standard time-based schedule or define a custom cron expression.

1

Select the Time unit, such as Minutes, Hours, or Days.

2

Specify the sync interval in the Trigger every field.

For example, if you select Hours as the Time unit and enter 12 in the Trigger every field, the pipeline syncs every 12 hours. The minimum interval you can set is 30 minutes.

Configure sync frequency

3

Select a start date for the historical data sync in the When first started, this pipeline should pick up records from field. This defines the earliest date from which the pipeline extracts records. If you leave this field blank, the pipeline picks up all available records from the source.

You can't change this value after you run the pipeline. Refer to the When first started, this recipe should pick up events from section for more information.

4

Click Save to save your progress before you configure your data pipeline destination.

1

Select Custom schedule in the Time unit field.

Configure sync frequency

2

Enter a Cron expression in the Cron expression field using the format:

[minute] [hour] [day of month] [month] [day of week]

The minimum interval for cron schedules is 15 minutes. For example, to sync every day at 8:00 AM UTC, enter:

0 8 * * *

3

Optional. Select a Timezone for the cron expression. Leave blank to use Etc/UTC.

4

Select a start date for the historical data sync in the When first started, this pipeline should pick up records from field. This defines the earliest date from which the pipeline extracts records. If you leave this field blank, the pipeline picks up all available records from the source.

You can't change this value after you run the pipeline. Refer to the When first started, this recipe should pick up events from section for more information.

5

Click Save to save your progress before you configure your data pipeline destination.

Supported Coupa objects

The Coupa connector uses the Coupa REST API to retrieve records for pipeline sync. It supports standard objects commonly used in Coupa environments, including accounts, approvals, and contracts.