> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-sage-crm-integration/sage-100/user-guide/vendor-integration/create-vendor-from-sage-100-to-sage-crm.md).
# Create Vendor from Sage 100 to Sage CRM
### Create Vendor from Sage 100 to Sage CRM
In GUMU™ we have also provided vendor sync feature from Sage 100 to Sage CRM on real-time basis with the click of Vendor maintenance screen accept button. To enable this functionality user will need to fill in the required details and have to uncheck the Inactive checkbox in the Sage 100 GUMU™ module screen. Refer to below image.
Using this, Sage CRM user can create/update vendor details/addresses and contacts from Sage 100 to Sage CRM on real time basis. For enabling real time create/update for any particular Sage 100 vendor record Sage CRM user have to check “Synchronization” checkbox present on vendor maintenance.
User can create/update below information if “Sync To CRM” checkbox is checked on Vendor maintenance in Sage 100.
#### Vendor Details:
#### Vendor Contacts:
#### Vendor Address:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.greytrix.com/gumu-sage-crm-integration/sage-100/user-guide/vendor-integration/create-vendor-from-sage-100-to-sage-crm.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.