Plex and Zendesk integration

What moves between them

Customer records and recent sales orders flow from Plex into Zendesk. When a support ticket is created or updated in Zendesk, ml-connector looks up the customer name or email in Plex and attaches the customer ID, recent order count, and last shipment date to the ticket as custom fields. The flow is one-way into Zendesk support because Zendesk has no order, invoice, or shipment entities to write back. On the Plex side, support tickets can be tagged with a Plex customer ID or reference a sales order number, linking ticket context back to manufacturing. The sync runs on a 5-minute interval for Plex polling and in real-time for Zendesk webhook events.

How ml-connector handles it

ml-connector stores Plex OAuth credentials encrypted and refreshes the Bearer token when a call returns 401. On the Zendesk side, it accepts OAuth 2.0 credentials and registers a webhook endpoint for ticket.created and ticket.updated events. When a ticket is created in Zendesk, the webhook triggers immediately, and ml-connector queries Plex for a customer record matching the ticket email or organization name. Plex polling runs on a 5-minute interval to catch sales order updates and shipment status changes. Customer lookup by email in Zendesk may match multiple organizations, so ml-connector stores the Plex customer ID in a custom field and checks it first on ticket updates to avoid re-querying. Zendesk webhook signatures are verified with HMAC-SHA256. If a Plex customer lookup fails, the ticket is still created in Zendesk but without order context, so the agent can manually link it later. Rate limits on Plex return HTTP 429 with no retry-after header, so ml-connector uses exponential backoff.

A real-world example

A mid-sized discrete manufacturer sells custom parts to automotive suppliers. When a customer calls Zendesk support about an order status or invoice question, the support agent has no visibility into when the part ships or when the invoice posted. Without the integration, the agent looks up the customer in Plex manually in another browser tab or calls the fulfillment team. With Plex and Zendesk connected, the agent opens the support ticket and sees the customer ID, recent order list, and last shipment date in the ticket sidebar. The agent answers order questions directly and routes escalations to the right team with context already in hand. Support response time improves, and fewer calls bounce between support and fulfillment.

What you can do

• •Sync customer records from Plex into Zendesk tickets so agents see customer history and order context.
• •Attach recent sales order and shipment information to support tickets via custom fields populated from Plex.
• •Match support ticket emails and organization names to Plex customers automatically on ticket create or update.
• •Listen to Zendesk ticket events via webhook and poll Plex on a configurable 5-minute interval for order status changes.
• •Verify Zendesk webhook signatures with HMAC-SHA256 and refresh Plex OAuth tokens transparently.

Questions

Which direction does data move between Plex and Zendesk?

Customer records and sales orders flow from Plex into Zendesk as ticket metadata and custom fields. Zendesk has no order, invoice, or payment entities, so there is no write-back. Support tickets in Zendesk can reference a Plex customer ID or sales order number for context, but the primary sync is enriching Zendesk tickets with Plex customer history.

How does the integration match customers between Plex and Zendesk?

ml-connector matches customers by email address or organization name in Zendesk to customer records in Plex. When a match is found, the Plex customer ID is stored in a custom field on the ticket so future updates can check that field first and avoid re-querying. If no match is found, the ticket is created without order context and the agent can link it manually.

Does Plex's lack of webhooks mean tickets are delayed?

No. ml-connector listens to Zendesk ticket creation events via webhook, so new tickets trigger a Plex customer lookup immediately. Plex order status changes are detected via a 5-minute polling interval, so agents see shipment updates within 5 minutes of a status change in manufacturing.