IFS Cloud and HubSpot integration

What moves between them

The main flow moves from IFS Cloud into HubSpot. Suppliers and customers from IFS Cloud's SupplierSet and CustomerSet are synced as HubSpot company objects, tagged with their GL account code, cost center, and financial dimensions. Invoices from IFS Cloud's PostingProposalHeadSet can be synced as HubSpot invoice objects, with line items created from the invoice details and associated to the correct company. The sync runs on a schedule you define, typically daily or after each billing cycle, so your sales and finance teams see the same customer view.

How ml-connector handles it

ml-connector stores IFS Cloud OAuth2 credentials (client_id and client_secret) encrypted and exchanges them for a bearer token at the IFS tenant's specific token endpoint. On the HubSpot side, it stores the private app token encrypted and uses it as a bearer token on every request. When reading from IFS Cloud's OData API, ml-connector manages pagination and ETag headers to handle IFS's concurrency requirement, so every update to an existing record captures the current ETag before mutating it. Because IFS Cloud is pull-only, ml-connector polls at your scheduled cadence and tracks which records have already been synced to avoid duplicates. Line items in IFS invoices are expanded from the OData array and mapped to HubSpot line items, then associated to the correct HubSpot company. HubSpot rate limits are managed with exponential backoff, and every record carries a full audit trail so failed syncs can be replayed when the issue is fixed.

A real-world example

A mid-market manufacturer runs IFS Cloud for finance, procurement, and supply chain, and uses HubSpot to manage customer relationships and track deals. Before the integration, the sales team maintained a separate spreadsheet of which customers also appeared in the finance system, and billing inquiries from customers required manual lookups in IFS to find the GL account and cost center. With IFS Cloud and HubSpot connected, every customer synced from IFS appears as a HubSpot company record tagged with their financial dimensions, so sales can see exactly which GL account a customer belongs to without leaving HubSpot. Invoices from IFS flow into HubSpot as closed deals and commerce records, giving the team a complete view of the customer relationship and financial position in one place.

What you can do

• •Sync IFS Cloud suppliers and customers to HubSpot as company records, tagged with GL account codes and financial dimensions.
• •Move invoices from IFS Cloud into HubSpot as commerce objects with full line-item detail and association to the correct company.
• •Bridge IFS Cloud OAuth2 credentials and HubSpot private app tokens, managing token refresh and encryption securely.
• •Handle IFS OData pagination, ETag concurrency headers, and the 5000-element per-request limit to avoid errors and data loss.
• •Poll IFS Cloud on a schedule you control, deduplicate records, and maintain a full audit trail for every sync.

Questions

What records move from IFS Cloud to HubSpot?

Suppliers and customers from IFS Cloud's master data are synced as HubSpot company objects. Invoices from IFS Cloud can be synced as HubSpot invoice objects with their line items and associated to the matching company. GL accounts and cost centers are mapped as company properties so your sales team can see the financial dimensions without leaving HubSpot.

Does ml-connector handle IFS Cloud's ETag requirement for updates?

Yes. ml-connector reads the ETag from IFS Cloud on each record, then includes it in the update request using IFS OData's If-Match header. This enforces optimistic concurrency and prevents lost updates if another process changes the record between read and write.

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

ml-connector polls IFS Cloud's OData API on a schedule you define, typically daily or after your billing cycle. It tracks which records have already been synced so duplicates are avoided, and it backs off and retries if IFS returns a rate-limit response.