Plex and Ramp integration

What moves between them

Bill events and transaction data flow from Ramp into Plex. When a bill is created, updated, or paid in Ramp, ml-connector captures the event via webhook and posts it into Plex's general ledger, mapped to the appropriate GL account and cost center. Vendor master data is synced in both directions so bills in Ramp reference suppliers that exist in Plex, and new suppliers in Plex can be made available in Ramp. Purchase orders and cost allocations are aligned bidirectionally to ensure Plex and Ramp agree on spending authority and cost tracking.

How ml-connector handles it

ml-connector stores both OAuth 2.0 credential sets encrypted and maintains separate access tokens for each system, refreshing them before expiry. On the Plex side it polls on a configurable schedule to read supplier changes and purchase order updates. On the Ramp side it subscribes to webhook events for bills, transactions, and vendor changes. When a Ramp bill webhook arrives, ml-connector verifies the HMAC-SHA256 signature, transforms the bill into a Plex journal entry, and posts it into the matching GL account and cost center. Vendor records are enriched with both Plex and Ramp identifiers so lookups work in both directions. Because Plex has no native webhooks, gl-account posts from Ramp are queued and processed in batches at night or on demand. Rate limits on the Plex side are handled with exponential backoff. Every record carries an audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized automotive parts supplier runs Plex for production, inventory, and purchasing, and Ramp for corporate cards, travel, and vendor bill pay. Before the integration, the accounting team received bills paid through Ramp and re-entered them into Plex's general ledger by hand, a process that took hours each week and introduced errors when bills were misallocated to the wrong cost center. With Plex and Ramp connected, each bill created in Ramp flows automatically into Plex's ledger, allocated to the correct department and project, and vendor master data stays in sync so all users see the same supplier information. Month-end close is faster because there is no backlog of bills waiting to be posted.

What you can do

• •Capture bill events in real-time from Ramp via webhooks and post them into Plex's general ledger with correct GL account and cost center allocation.
• •Sync vendor master records bidirectionally between Ramp and Plex so new suppliers in either system are available to both.
• •Align purchase orders and cost centers across Plex and Ramp so spending authority and budget allocations are enforced consistently.
• •Authenticate with OAuth 2.0 on both Plex and Ramp, verify Ramp webhook signatures with HMAC-SHA256, and refresh tokens before expiry.
• •Poll Plex on a configurable schedule for supplier and purchase order changes while receiving Ramp bill and transaction events in real-time via webhook.

Questions

Which direction does data move between Plex and Ramp?

Bills and transactions flow primarily from Ramp into Plex's general ledger. Vendor master data is synced in both directions so suppliers created in either system are available to both. Purchase orders and cost allocations are also aligned bidirectionally to ensure Plex and Ramp agree on procurement and cost tracking.

How does ml-connector handle the difference between Plex polling and Ramp webhooks?

Plex has no native webhooks, so ml-connector polls the Plex API on a configurable schedule to read supplier and purchase order changes. Ramp publishes real-time webhook events for bills, transactions, and vendors, which ml-connector receives and verifies with HMAC-SHA256 signature checks before posting into Plex.

What happens when a bill is created in Ramp? How long until it appears in Plex?

ml-connector receives the bill event immediately via Ramp's webhook, verifies the signature, and queues the journal entry. The entry is posted into Plex's general ledger on your configured schedule, typically within minutes. If the vendor or cost center does not yet exist in Plex, ml-connector queues the bill and retries after syncing the missing reference data.