WinThor
Connect WinThor to your company operations. Review required fields, credential setup and how this connector works in Zild.
Connect WinThor to your company operations.
Where to configure
Open Zild Admin → Integrations → Connectors, find the provider and use Configure or Edit. Enter the data from this guide, enable the connector for the workflow and save.
Your company credentials
Customers must obtain and configure their own API keys or the authentication method required by this connector. The Zild subscription is based on company size; external service usage is billed separately by the respective provider. You do not need to configure connectors your operation does not use.
Required fields
These requirements are the data needed by the workflow using the connector. Generic saving may accept empty fields that are only required when an operation runs. Saving does not confirm that the provider accepts the credential.
| Field | Workflow requirement |
|---|---|
Url | WinThor service HTTPS base URL, without appending the login or operation path. |
CustomProperties.Login | WinThor user login. |
ApiSecret | Original user password; do not enter a hash. |
How to obtain credentials
- Ask your WinThor administrator for an integration user, password and the HTTPS authentication/API base URL.
- Fill CustomProperties.Login and ApiSecret with the original login and password. Zild performs the conversion required by WTA; do not paste a hash or send the password to external converters.
- In Url, enter the service base without appending winthor/autenticacao/v1/login. Zild adds that path when authenticating; confirm the deployment prefix with your administrator.
- Confirm access to customers, products, inventory and orders used by the agent. User creation depends on the installation; consult the TOTVS administrator.
How it works in Zild
Zild obtains the session token from the login; no manually copied API key is required.
How to verify the configuration
After saving, use the matching workflow (query, agent, call or processing) to verify access. If it fails, check the credential, permissions and selected provider resource. For limited or legacy types, confirm availability with your administrator before use.
When editing, Zild displays protected credentials as asterisks. Preserve the masked value to keep the current credential or paste a new credential to replace it.
Official documentation
Check the selected connector type and connection
Register and explicitly select the WinThor type. Filling Login or using “WinThor” in the name does not turn a connection of another type into a WinThor connection. The tool requires an enabled connection of the correct type belonging to the same company.
If an older record is unavailable for selection, check its type, company and status with your administrator before creating another record. Also review dependent tools; correcting configuration does not imply rerunning previous orders.
Configure commercial rules in the connector
Alongside login credentials, confirm the branch (BranchId), company (CompanyId), cash billing code (CashBillingId), cash payment plan (CashPaymentPlanId) and issuing employee (EmployeeId) with your ERP administrator, according to the enabled operations. Each tool requires its mandatory operation fields and uses the connector configuration for these values even if the agent supplies a different argument.
Use codes confirmed in your environment. The billing code accepts up to four characters; the other configured codes above must be positive integers without leading zeros. Configuration does not replace ERP permissions or commercial validation.
When reviewing an older tool, move confirmed fixed codes into the connector configuration before saving and testing. Legacy tool values or agent-supplied arguments do not replace a missing required connector setting. Connector changes apply to tools using that connection; review all dependent processes before changing the branch or commercial conditions. Do not duplicate property names using different capitalization.
Customer territory and sales price table
RegiaoId in the customer record represents the territory region. It does not establish the customer/branch sales table relationship from routine 3314. Confirm regiaoPrecoId with the sales team; do not infer it from the state, territory or a list of regions returned by the API.
When pricing depends on the region from routine 201 and the ERP has not returned a valid fixed-price campaign, the integration requires the confirmed table. If it returns tabela_venda_nao_informada or tabela_venda_nao_retornada, check the customer, branch and table before proceeding. A missing price in the response does not prove that the table does not exist in WinThor. Selecting regiaoPrecoId does not change the ERP record relationship.
For customer creation, the reference branch (dados.branchParameterId) is populated from the connector’s BranchId setting. The sales area (dados.squareId) remains a required tool input, confirmed for the customer. The API does not provide an automatic sales-area mapping by postal code. Confirm that mapping with the ERP owner; do not use another customer’s sales area as a default. If an option list fails, entering a code manually does not validate that it matches the address.
To diagnose a missing price table, record clienteId, filialId, produtoId, regiaoPrecoSolicitadaId and regioesPrecoDisponiveis from the response. Available regions help the ERP team investigate the integration; they do not authorize automatically selecting another table. Resolve missing or ambiguous pricing before presenting a price as confirmed.
Check the result before retrying or confirming
When creating a customer, supply the territory confirmed for the address. If registradoNoErp=true is returned with cadastro_divergente or cadastro_registrado_conferencia_pendente, the record has already been created: do not repeat creation. Check the territory and postal-code rules in the ERP before proceeding with a sale.
Order creation requires approval, a quote reference and the commercial revision. Conditions are retrieved again; condicoes_alteradas_confirmacao_necessaria indicates that the approved revision changed and needs another review. In staging, validate a price query, customer creation with territory verification and a quote before enabling real orders. Do not invent prices, package conversion factors or missing codes.