Which direction does data move between SAP S/4HANA and Zoho CRM?

The main flow is from SAP S/4HANA into Zoho CRM. Supplier and customer master records, company details, and contact information move from SAP into Zoho, where they map to vendors and accounts. SAP GL accounts and cost centers are read-only in the API, so financial dimensions do not sync back to Zoho.

How does ml-connector handle SAP token expiry and Zoho region-specific domains?

ml-connector caches SAP tokens before the 12-hour expiry and refreshes from the Communication Arrangement endpoint. For Zoho, it extracts the api_domain from each token response and routes subsequent requests to the correct region (com, eu, in, com.au, jp, ca, com.cn), so multi-region deployments work without manual configuration.

Does this integration require SAP webhooks or Zoho webhook setup?

No. SAP S/4HANA offers no webhooks, so ml-connector polls SAP on a schedule you control using LastChangeDateTime filters. Zoho CRM can optionally push notifications, but ml-connector also polls Zoho if webhooks are not set up, and it automatically renews webhook channels before they expire every 24 hours.

SAP S/4HANAZoho CRM

SAP S/4HANA and Zoho CRM integration

SAP S/4HANA runs procurement and finance. Zoho CRM runs sales and customer management. Connecting them keeps your supplier and customer master records in agreement across both systems. Suppliers created in SAP appear in Zoho as vendors, and customers created in SAP sync as accounts so your sales team sees the complete picture. ml-connector bridges the different APIs and authorization models on each side, and moves the data on a schedule you control.

How SAP S/4HANA works

SAP S/4HANA exposes business partners, suppliers, customers, purchase orders, invoices, GL accounts, and cost centers through OData V2 and OData V4 REST APIs over HTTPS. Authentication is OAuth 2.0 Client Credentials, with scopes defined per Communication Arrangement in each SAP tenant. Tokens are short-lived, typically 12 hours, so they must be cached and refreshed before expiry. SAP S/4HANA publishes no native webhooks, so partner records are read by polling with filter conditions on the LastChangeDateTime field or using delta tokens for initial sync. GL Accounts and Cost Centers are read-only in the API.

How Zoho CRM works

Zoho CRM exposes accounts, contacts, vendors, deals, quotes, and purchase orders through a REST API available in Professional edition and above. Authentication is OAuth 2.0, with an access token valid for 1 hour and a refresh token for offline access. The token response includes an api_domain field that must be used as the base URL for subsequent requests, as Zoho operates across region-specific domains. Zoho CRM supports webhooks for create, edit, and delete events, but notification channels expire every 24 hours and must be renewed before they lapse. Webhook payloads contain only record IDs, so ml-connector must fetch full records after notification.

What moves between them

The main flow is from SAP S/4HANA into Zoho CRM. Supplier and customer master records flow from SAP into Zoho, where they map to vendors and accounts. SAP business partner roles determine the record type: roles marked as supplier map to Zoho vendors, and roles marked as customer or sold-to party map to Zoho accounts. Contact details, tax IDs, and payment terms flow in the same direction. The integration runs on a schedule tied to your procurement or sales cycle rather than waiting for a push from SAP, since SAP offers only pull-based APIs.

How ml-connector handles it

ml-connector stores the OAuth credentials for both systems encrypted and manages token refresh independently on each side. On the SAP side, it caches tokens before the 12-hour expiry window and uses the Communication Arrangement token endpoint per customer, since SAP publishes no universal token URL. On the Zoho side, it extracts and uses the api_domain from the token response so requests route to the correct region (com, eu, in, com.au, jp, ca, com.cn). SAP business partner data arrives via polling with LastChangeDateTime filters, while Zoho can also receive webhook notifications if channels are set up. When a webhook channel nears its 24-hour expiry, ml-connector renews it via a PATCH request before it lapses, so push notifications do not go silent. Contact details and company information are mapped carefully so SAP supplier codes align with Zoho vendor IDs and customer names are consistent across systems.

A real-world example

A mid-sized distribution company runs SAP S/4HANA for procurement and order fulfillment, and Zoho CRM for sales and customer management. Before the integration, the sales team manually entered customer details into Zoho from spreadsheets or sales calls, and the procurement team maintained a separate master list of suppliers in SAP with no visibility to sales. Duplicate accounts, mismatched company names, and stale contact details created friction during customer onboarding and supplier negotiations. With SAP S/4HANA and Zoho CRM connected, every supplier registered in SAP automatically appears in Zoho as a vendor, and every customer in SAP syncs as an account, so the sales team sees the complete party hierarchy and historical SAP transaction data during customer conversations.

What you can do

Sync SAP S/4HANA suppliers into Zoho CRM as vendors, keeping procurement and sales teams aligned on partner master data.
Sync SAP S/4HANA customers into Zoho CRM as accounts, so sales has visibility into customer hierarchies and payment terms.
Map SAP business partner roles to Zoho record types, so suppliers and customers sort into the correct CRM module.
Manage OAuth 2.0 on both sides independently, refresh tokens before expiry, and handle Zoho region-specific API domains.
Poll SAP on a schedule tied to your business cycle, with full audit trail on every record change.

Questions

Which direction does data move between SAP S/4HANA and Zoho CRM?: The main flow is from SAP S/4HANA into Zoho CRM. Supplier and customer master records, company details, and contact information move from SAP into Zoho, where they map to vendors and accounts. SAP GL accounts and cost centers are read-only in the API, so financial dimensions do not sync back to Zoho.
How does ml-connector handle SAP token expiry and Zoho region-specific domains?: ml-connector caches SAP tokens before the 12-hour expiry and refreshes from the Communication Arrangement endpoint. For Zoho, it extracts the api_domain from each token response and routes subsequent requests to the correct region (com, eu, in, com.au, jp, ca, com.cn), so multi-region deployments work without manual configuration.
Does this integration require SAP webhooks or Zoho webhook setup?: No. SAP S/4HANA offers no webhooks, so ml-connector polls SAP on a schedule you control using LastChangeDateTime filters. Zoho CRM can optionally push notifications, but ml-connector also polls Zoho if webhooks are not set up, and it automatically renews webhook channels before they expire every 24 hours.

Connect SAP S/4HANA and Zoho CRM

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started