Microsoft Dynamics GP and Zendesk integration

What moves between them

The primary flow runs from Dynamics GP into Zendesk. Vendor records and customer records are pulled from Dynamics GP and synced as Organizations and Users in Zendesk. Recent invoices (payables and receivables) are fetched and stored as custom fields or ticket comments to provide context within support tickets. GL accounts appear in organization metadata so support agents can route financial inquiries. The sync runs on a schedule you control, typically once per hour, with no push notifications from Dynamics GP.

How ml-connector handles it

ml-connector accepts the customer's Dynamics GP endpoint URL and Windows domain credentials, polls Dynamics GP's SBA or SOAP interface using ModifiedDate filters to find records changed since the last run, and maps the retrieved vendor and customer records to Zendesk Organizations and Users. Invoice details are attached to the matching customer organization as notes or custom fields. Because Dynamics GP is on-premises and pull-only, ml-connector cannot register a webhook on Dynamics GP itself, so it relies on polling with rate-limiting to avoid overloading the customer's SQL Server. The Windows auth flow requires the customer to create a dedicated domain account and configure firewall access to the SBA endpoint. Posted transactions in Dynamics GP are read-only, so ml-connector never writes invoices or GL entries back into Dynamics GP. Each poll carries a full audit trail, and failed syncs can be replayed once any upstream issue is resolved.

A real-world example

A mid-market business-software vendor manages customer accounts and contractual payables in Dynamics GP. When a customer support request arrives in Zendesk, the support team has to manually search Dynamics GP for the customer's balance or recent invoice details, then paste the information into Zendesk. With Dynamics GP and Zendesk connected, each customer becomes an Organization in Zendesk with their current AR balance and recent invoices visible in the ticket context, and the support team answers faster with the financial picture always at hand.

What you can do

• •Sync vendors and customers from Dynamics GP into Zendesk Organizations, keeping buyer and supplier context in every ticket.
• •Attach recent payables and receivables invoices from Dynamics GP to the matching Zendesk organization as searchable notes or custom fields.
• •Map Dynamics GP GL accounts to Zendesk organization custom fields so support agents route financial inquiries to the correct team.
• •Authenticate Dynamics GP with Windows Active Directory and Zendesk with OAuth 2.0, bridging a legacy on-premises ERP to a cloud support platform.
• •Poll Dynamics GP on a schedule tied to your business cycle, with retries and full audit trail on every vendor, customer, and invoice record.

Questions

How does ml-connector bridge Windows Active Directory authentication in Dynamics GP to cloud OAuth in Zendesk?

ml-connector accepts Windows domain credentials (username and password) and constructs the SBA or SOAP request with those credentials in the Authorization header using Negotiate or NTLM negotiation. On the Zendesk side, ml-connector holds a persistent OAuth 2.0 access token obtained once at setup. The two auth flows are independent; ml-connector translates data from one to the other without requiring the support agent to hold a Dynamics GP login.

What records move between Dynamics GP and Zendesk, and in which direction?

The primary flow is from Dynamics GP into Zendesk. Vendor and customer master records become Zendesk Organizations; their contacts (users) become Zendesk Users. Recent invoices are attached as organization notes or custom fields. GL accounts and cost centers are mapped to custom fields for routing. Dynamics GP is read-only for ml-connector, so support tickets and customer interactions in Zendesk never flow back into the ERP.

Does Dynamics GP support webhooks, or does ml-connector have to poll?

Dynamics GP has no native webhook system, so ml-connector polls the SBA or SOAP endpoint at a schedule you define, typically hourly. Polling uses ModifiedDate filters to fetch only changed records since the last run, which minimizes SQL Server load. The customer must expose the Dynamics GP endpoint through the firewall and provide a Windows domain account for polling to succeed.