IFS Cloud and Zoho CRM integration

What moves between them

The main flow runs from IFS Cloud into Zoho CRM. Customer records from IFS Cloud are synced to Zoho CRM as accounts, mapped by customer code or customer number. Sales orders from IFS Cloud are synced into Zoho CRM as deals, with the order number, customer reference, and sales amount preserved. Changes to customers and orders in IFS Cloud flow into Zoho CRM on a pull schedule, typically once per hour or tied to your sales process timing. Zoho CRM is write-mostly for the CRM team, so ml-connector reads customer and deal data from Zoho for reference but does not write back into IFS Cloud.

How ml-connector handles it

ml-connector stores both credential sets encrypted and handles OAuth2 client credentials on the IFS Cloud side, refreshing tokens when they expire (approximately 60-minute lifetime). On the Zoho CRM side, it manages the OAuth2 access token (1-hour lifetime) and refresh token for long-lived access. Because IFS Cloud offers no self-registerable webhooks, ml-connector polls the OData API on a configurable schedule, filtering by created or modified timestamp to capture only new and changed records. When Zoho webhook notifications are enabled, ml-connector receives channel expirations and automatically renews them before they lapse, preventing notification loss. Customer records are matched by customer number, so duplicate accounts in Zoho are avoided. Sales orders from IFS Cloud include customer reference, order lines, and sales amount, mapped into Zoho deal records with the customer link established via the matched account. IFS Cloud requires an ETag header on mutation operations, enforced via optimistic concurrency, though ml-connector primarily reads from IFS Cloud and posts into Zoho CRM. Rate limits on both sides are respected with exponential backoff and jitter when either system returns 429 or 500. Every record carries a full audit trail, and failed syncs can be retried without duplicating records already in Zoho CRM.

A real-world example

A mid-market manufacturing company runs IFS Cloud for operations and finance, managing customers, sales orders, and cost allocation across multiple plants. The sales team uses Zoho CRM to track pipeline and forecast. Before the integration, the sales team manually re-entered new customers from the finance system into Zoho CRM, and high-value sales orders in IFS Cloud were logged as Zoho deals only when the sales rep remembered to open both systems. With IFS Cloud and Zoho CRM connected, each new customer added to finance appears in Zoho within the hour, and sales orders from IFS Cloud automatically populate as deals with the correct customer link and order total, so the sales pipeline and the financial forecast stay aligned without manual re-entry.

What you can do

• •Sync customers from IFS Cloud into Zoho CRM as accounts, matched by customer number to prevent duplicates.
• •Automatically create deals in Zoho CRM from IFS Cloud sales orders, with customer links and order amounts.
• •Refresh OAuth2 tokens on both sides and handle client credentials across different security models.
• •Poll IFS Cloud on a schedule tied to your sales process, with retries and exponential backoff when rate limits are hit.
• •Receive and renew Zoho CRM webhook notification channels automatically before expiration.

Questions

Which direction does data flow between IFS Cloud and Zoho CRM?

The primary flow is from IFS Cloud into Zoho CRM. Customer records from IFS Cloud are synced to Zoho as accounts, and sales orders are synced as deals. Zoho CRM is used by the sales team for pipeline and forecasting, so ml-connector reads from Zoho for reference but does not write customer or order changes back into IFS Cloud.

How does ml-connector handle IFS Cloud's lack of self-registerable webhooks?

IFS Cloud requires manual webhook configuration in the admin UI and does not provide a self-registerable API. ml-connector polls the IFS Cloud OData API on a configurable schedule, filtering by modified timestamp to capture only new and changed records. This pull-based approach avoids the need for per-customer webhook setup.

What happens when OAuth2 tokens expire on either side?

IFS Cloud OAuth2 tokens expire after approximately 60 minutes, and Zoho CRM tokens expire after 1 hour. ml-connector stores refresh tokens encrypted and automatically refreshes access tokens before they expire, so the integration continues without interruption. If a token does expire in-flight, the next scheduled poll refreshes it and retries the request.