Coupa Destination for Reverse ETL Request
Which business application?: Coupa (procurement platform).
What object in the destination?:
Two objects, via Coupa's REST API:
1. Invoice payment status — update invoices to "Paid" status once payment
is confirmed (Coupa Invoices API)
2. Supplier records — create new suppliers and update existing supplier
master data (Coupa Suppliers API)
How will records be identified?:
Payments matched by Coupa invoice ID
(or invoice_number + supplier_number). Suppliers matched by Coupa
supplier ID / external reference; new vs. existing determined by whether
a matching supplier record already exists in Coupa.
What sync behaviour?:
- Payments: incremental upsert — update payment/paid status on invoices
as they cleared.
- Suppliers: incremental upsert — insert new suppliers, update changed
fields on existing suppliers; unchanged suppliers skipped.
Additional context:
We currently push this data to Coupa via an SFTP-based
CSV file drop (custom AWS Lambda + PostgreSQL staging pipeline). We'd like
to move away from SFTP/file-based delivery entirely and use Coupa's REST
API instead, since it supports proper record-level upserts and status
updates rather than batch file processing. We're rebuilding our data
platform natively in Snowflake and would like Fivetran Activations to
write directly from Snowflake to Coupa via its API.
Please sign in to leave a comment.
Comments
0 comments