Microsoft Dynamics GP and Twilio integration

What moves between them

The integration flows from Microsoft Dynamics GP into Twilio. ml-connector polls the GP payables ledger on a schedule you set, checking for overdue invoices, newly posted POs, and payment transactions. When thresholds are met (invoice aged 30+ days, PO awaiting vendor acknowledgment, payment posted), ml-connector looks up the vendor or customer contact number stored in GP and sends an SMS through Twilio or initiates a voice call. Vendor names and amounts are included in the message template. The integration is read-only on the GP side; no transactions are written back to Dynamics GP.

How ml-connector handles it

ml-connector stores Windows domain credentials for GP and Twilio API credentials encrypted at rest. On the GP side, it connects via the REST Service Based Architecture endpoint using Windows auth and polls the Payables Invoices, Purchase Orders, and GL Journal tables with ModifiedDate filters to detect changes. Because GP is on-premises, the customer must expose the SBA endpoint through a firewall or local agent; ml-connector validates the endpoint and certificate at setup. On the Twilio side, ml-connector presents HTTP Basic Auth with the Account SID and Auth Token on each REST call. It maintains a mapping of vendor records to Twilio phone numbers, either stored in a custom GP field or in a separate contact lookup table. When a notification triggers, ml-connector sends a templated SMS via the Twilio Messaging API or initiates a call via the Voice API. Twilio webhooks return status callbacks; ml-connector listens for delivered and failed messages to complete the audit trail. Windows auth requires a dedicated domain account with appropriate GP security roles; the customer creates and manages this account. The polling interval is customer-defined; aggressive polling can degrade GP end-user performance, so typical cadence is 15 minutes to hourly. All records and payloads are logged in the audit trail, and failed notifications can be replayed.

A real-world example

A mid-sized specialty distributor runs Microsoft Dynamics GP for AR, AP, and inventory on a local Windows Server. The finance team spends hours chasing overdue invoices and payment confirmations by email, and procurement staff miss purchase order updates because they are buried in GP task lists. The company wants SMS alerts when invoices are overdue, a text message sent to the vendor as soon as payment is processed, and an SMS to the buyer when a PO is acknowledged. ml-connector polls the GP payables and GL ledgers every 30 minutes, detects status changes, looks up phone numbers from the vendor master, and sends SMS and voice alerts through Twilio. Overdue invoices trigger an alert to the finance manager's phone. Payments posted to GL fire a confirmation message to the vendor's registered number. PO acknowledgments generate a message to the procurement team. The process is automated, the audit trail is complete, and the manual email chase is gone.

What you can do

• •Poll Microsoft Dynamics GP payables invoices, purchase orders, and GL journals on a schedule you set, detecting aging and status changes.
• •Send SMS alerts through Twilio when invoices become overdue, purchase orders require action, or payments are posted.
• •Map vendor and customer records in GP to phone numbers and send templated SMS or voice calls with amounts and dates.
• •Encrypt Windows domain credentials and Twilio API keys at rest, present Windows auth to GP and HTTP Basic Auth to Twilio, and log every notification in an audit trail.
• •Replay failed notifications and track Twilio webhook callbacks for message delivery status without re-polling or manual intervention.

Questions

Why is this integration necessary if both systems have APIs?

Microsoft Dynamics GP is on-premises and does not support webhooks or push notifications, so changes must be polled. Twilio is a communications API, not an ERP, so it has no knowledge of financial events on its own. The integration bridges the gap by polling GP for payables changes and translating them into SMS and voice calls through Twilio. This keeps teams informed in real time without manual escalation.

How does ml-connector handle Windows authentication for Dynamics GP?

The customer creates a dedicated Windows domain account with the necessary GP security roles for reading payables and GL tables. ml-connector stores this credential encrypted and presents it via Windows Negotiate/Kerberos or NTLM on each REST call to the Service Based Architecture endpoint. Because GP is on-premises, the endpoint must be exposed through a firewall; ml-connector validates the SSL certificate at setup.

What happens if a Twilio SMS fails to deliver?

Twilio returns a webhook callback with the final delivery status (sent, delivered, failed, undelivered). ml-connector logs the failure in the audit trail and keeps the notification record available for replay. The customer can view the failed notification in the ml-connector dashboard and resend it manually or configure automatic retry rules per message type.