> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/integrations/coupa-integration/supplier-sync.md).
# Supplier sync
With the supplier sync, your suppliers created in Coupa are imported and created or updated in Fairmarkit. This is completed with a scheduled job.
### Import suppliers into Fairmarkit
Based on a scheduled job, Fairmarkit will import your suppliers created in Coupa into Fairmarkit.
The scheduled job does the following:
* Finds all suppliers.
* Maps your Coupa data to be used in Fairmarkit.
* #### Supplier data
| Coupa field | Fairmarkit field |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
|
Number or ID
Note: The selected value depends on your configuration.
| External Supplier Id |
|
Display Name or Name
Note: The process checks in order and the first found value is selected.
| Title |
|
Primary Contact Email, Supplier email address, or PO Email.
Note: The process checks in order and the first found value is selected.
| Email |
| Primary Contact Phone-Work | Phone Number |
| Primary Address Street 1 | Address 1 |
| Primary Address Street 2 | Address 2 |
| Primary Address City | City |
| Primary Address State | State |
| Primary Address Postal Code | Zip |
| Primary Address Country Code | Country |
* Creates or updates suppliers in Fairmarkit.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.fairmarkit.com/buyers/integrations/coupa-integration/supplier-sync.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
