Plex and Slack integration

What moves between them

Data flows from Plex into Slack. Purchase orders, invoices, supplier shipments, and production events are polled from Plex on a configurable interval and posted as messages to Slack channels. Each message includes the Plex entity type, timestamp, and a link back to Plex for detailed reference. Slack is read-only for this integration; ml-connector does not write workflow actions back into Plex.

How ml-connector handles it

ml-connector stores Plex OAuth2 credentials and polls the REST API at a schedule you configure (5-15 minutes recommended per Plex constraints), filtering by modified_date to detect new and changed records. It handles Plex role-based permissions by using an integration user with the correct roles assigned, and respects company code (PCN) partitioning for SOAP queries. For Slack, ml-connector either posts messages via chat.postMessage or registers a webhook endpoint to receive Slack events. If using webhooks, it validates each incoming request's HMAC-SHA256 signature and verifies the timestamp is not older than 5 minutes, rejecting invalid requests. Message posting is paced to stay under Slack's one-message-per-second per channel limit. When a Plex API call returns HTTP 429 (rate limit), ml-connector backs off exponentially and retries. Every record carries a full audit trail and the Slack message ID for traceability.

A real-world example

A mid-sized discrete manufacturer runs Plex for operations, procurement, and supply chain across two plants. Their supply chain team uses Slack for daily coordination but relied on email alerts and manual Plex checks for supplier shipments and purchase order status. With Plex and Slack connected, each supplier delivery that Plex records triggers a message to the receiving channel with the PO number, part count, and expected vs received quantities, and invoice arrivals post to a dedicated finance channel with line items and amounts. Production alerts from the MES module notify the operations team instantly on Slack when quality issues or delays occur. The team responds to alerts in Slack and links back to Plex to take action, eliminating inbox clutter and keeping suppliers and production in sync across both locations.

What you can do

• •Post Plex purchase orders and releases to Slack channels whenever they are created or modified, with supplier names, amounts, and line item summaries.
• •Send supplier invoice notifications to a finance channel, including invoice number, amount due, GL account code, and date received for quick reconciliation.
• •Alert the operations team when production events, quality issues, or inventory variances are detected in Plex, routed by plant or work center.
• •Handle Plex OAuth2 token refresh and Slack webhook signature validation automatically while respecting Slack's one-message-per-second per channel rate limit.
• •Maintain a full audit trail of every message posted and every Plex record processed, with source transaction IDs and timestamps for replay.

Questions

How does the integration handle Plex's lack of native webhooks?

ml-connector polls the Plex REST API or legacy SOAP datasources on a configurable interval (5 to 15 minutes recommended), filtering by modified_date or created_date to find new records. This polling approach is the only way to detect changes in Plex since it offers no push notifications. The poll schedule can be tuned to match your operational tempo and peak order volumes.

What authentication does ml-connector handle between Plex and Slack?

ml-connector stores Plex OAuth2 client credentials and refreshes the bearer token automatically when an API call returns 401. For legacy SOAP queries, it stores Basic auth credentials with the company code (PCN). For Slack, it stores OAuth2 tokens and validates webhook signatures using HMAC-SHA256 with the X-Slack-Signature header, rejecting any request with an invalid signature or timestamp older than 5 minutes.

Which Plex records can be sent to Slack and in what direction?

Purchase orders, releases, invoices, suppliers, parts, sales orders, GL accounts, and production events from Plex flow into Slack channels as messages. Slack is read-only for this integration; ml-connector does not write anything back to Plex. You control the mapping between Plex record types and Slack channels through the configuration.