SYSPRO and Pipedrive integration

What moves between them

The main flow runs from SYSPRO into Pipedrive. ml-connector polls SYSPRO's customer master table and sales order headers on a regular schedule (typically every 10 to 15 minutes), then creates or updates matching organizations and deals in Pipedrive with the customer name, order number, order date, line items, and any custom fields you map. Inventory levels and warehouse stock from SYSPRO enrich each organization record, so sales reps see current stock status without leaving Pipedrive. No data flows back from Pipedrive into SYSPRO; the connection is read-only from SYSPRO's perspective.

How ml-connector handles it

ml-connector stores both credential sets encrypted: SYSPRO server URL, operator code, and OData password for the ERP side; Pipedrive API token or OAuth2 client credentials on the CRM side. It polls SYSPRO's OData layer (read-only, no write locks) using $filter on timestamp fields such as OrderDate and LastModified to detect new and changed records since the last run. For each new customer, ml-connector creates a Pipedrive organization; for each sales order, it creates a deal linked to that organization and populates custom fields with order date, amount, and line-item details. SYSPRO session tokens expire on logoff, so ml-connector refreshes credentials before each poll cycle. Pipedrive rate limits are enforced per plan (30,000 base tokens daily, multiplied by plan tier and seat count), so ml-connector tracks token consumption and backs off gracefully when limits approach. Every poll run and every sync record carries a full audit trail, so you can replay any failed record.

A real-world example

A mid-sized industrial distributor uses SYSPRO for order management, inventory, and finance, and Pipedrive for prospecting and pipeline visibility. Before integration, the sales team manually entered prospect information into Pipedrive, then checked SYSPRO separately to see if a prospect was already a customer or if an order was in backlog. Month-end, sales ops had to reconcile outstanding deals against SYSPRO's open orders by hand. With SYSPRO and Pipedrive connected, each new SYSPRO customer is automatically seeded as an organization in Pipedrive, and open orders appear as deals with current shipment status and line-item details. Sales reps work from a single view: they see each prospect's complete history and current orders without context-switching, and backlog reconciliation at month-end is automatic.

What you can do

• •Create organizations in Pipedrive from SYSPRO customer master records, keeping names, billing addresses, and custom attributes in sync.
• •Populate deals in Pipedrive from SYSPRO sales order headers, including order date, amount, and line-item detail.
• •Enrich organizations with real-time inventory levels and warehouse stock from SYSPRO so sales reps see available-to-promise without re-keying.
• •Authenticate SYSPRO with session tokens and HTTP Basic Auth, and Pipedrive with API tokens or OAuth2 bearer tokens.
• •Poll SYSPRO on a regular schedule with retries and a full audit trail on every record, with no writes back to the ERP.

Questions

Which direction does data move between SYSPRO and Pipedrive?

The flow is one-way: SYSPRO into Pipedrive. Customer masters become organizations, and open sales orders become deals. Inventory and warehouse stock enrich each organization. Pipedrive changes (deal stage updates, notes, custom field edits) stay in Pipedrive and do not flow back into SYSPRO.

Does the integration handle SYSPRO's polling-only architecture?

Yes. ml-connector polls SYSPRO's OData layer on a schedule you set (typically 10 to 15 minutes), filtering on timestamp fields such as OrderDate and LastModified to detect new and changed records since the last run. SYSPRO has no webhook system, so polling is the only option.

How does ml-connector handle session token expiry and Pipedrive rate limits?

ml-connector refreshes SYSPRO session tokens before each poll cycle to avoid logoff timeout. On the Pipedrive side, it tracks daily token consumption against your plan tier and seat count, and backs off gracefully when limits approach. Both systems carry a full audit trail so any failed record can be replayed.