Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Coupa connector, add new columns

Answered
Dangel Chacon User

Connector name: erd (coupa)

Table name: QUOTE_REQUEST

Column to add: Public Event

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-request/public

Column to add: Event Currency

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/currency/code

Column to add: Tags

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/tags

Column to add: Planned Savings

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/planned-savings

Additionally, the associated currency will be under: quote-requests/planned-savings-currency/code

Column to add: Negotiated Savings

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/negotiated-savings

Additionally, the associated currency will be under: quote-requests/negotiated-savings-currency/code

Column to add: Participation

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/quote-suppliers/quote-supplier/participation

Column to add: Followed from Event ID

Available: YES (confirm satisfaction)

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/original-id

Column to add: Create at

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path:   quote-request/create-at

Column to add: state

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/state

Column to add: Original id

Available: YES

API endpoint: GET - https://cemex.coupahost.com/api/quote_requests/{:id}

API technical path: quote-requests/original-id

 

Table name: CONTRACT

Column to add: 

Available: YES

Business Object: contracts

API endpoint: GET - https://cemex.coupahost.com/api/contracts/{:id}/contract_rounds

API technical path for relevant information discussed lately:

reviews

Path to the array with nested data within each element: /contract_rounds/reviews

counterparty_reviews

Path to the array with nested data within each element: /contract_rounds/counterparty_reviews

 

Additional details: Coupa's current APIs return the new columns; however, these columns do not appear in the Fivetran connector and cannot be selected.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Tom Jose Fivetranner

    Hi Dangel,



    This is a valuable idea, and we have added your request to our feature improvements backlog. To help us better prioritize and scope this enhancement, can you share more about your use case? For example, what specific analysis or business decisions do you hope to enable with these additional columns in the QUOTE_REQUEST and CONTRACT tables? Understanding the problems you're trying to solve will help us align our efforts with your needs.



    We will keep the community updated on this thread with any progress.



    Thanks,

    Tom

  • Dangel Chacon User
    The main objective of obtaining CLM data from COUPA is to enable operational and executive visibility across the contract lifecycle, supporting Legal teams and business stakeholders with reliable, structured, and traceable information. This data will allow us to build dashboards and reports that monitor contract request volume, current status, workload distribution, cycle times, requester-related delays, legal ownership, comments, and demand by business area.
    By consuming this information directly from COUPA, we aim to centralize reporting, reduce manual tracking efforts, and provide a consistent source of truth for decision-making. These insights will help identify bottlenecks, measure process performance, prioritize follow-up actions, support workload management, and enable continuous improvement of the CLM process across Legal and Procurement-related activities.
    In summary, the purpose of these use cases and reports is not only to visualize contract data, but to transform COUPA information into actionable insights that improve governance, transparency, efficiency, and accountability throughout the end-to-end contract management process.
     

    Additionally, it is possible to add the following columns: upon reviewing the response from the GET /api/contracts/{contract_id} API, we identified that relevant contract information is present in the source payload.
    The missing information includes:

    • The `contract_parties` array, which contains information about the contract parties and their addresses.
    • Custom fields located within nested containers or arrays, such as (note that these are not the only missing custom field arrays):
    • `contract_parties_field_containers`
    • `contract_termination`
    • `contract_performance`
    • `contract_risks`
    • `contract_price_and_payment`