IFS Cloud and Zendesk integration

What moves between them

The main flow is IFS Cloud into Zendesk. Supplier invoices from IFS Cloud are synced into Zendesk as organization records with custom fields capturing invoice number, amount, and payment status. Vendor contact details and purchase order references are added to ticket organization context so support agents have procurement history at hand. On the Zendesk side, ticket resolution status can trigger reference updates in IFS Cloud if needed. Data flows on a polling schedule tied to your accounts-payable cycle; Zendesk webhooks can also notify ml-connector of ticket status changes.

How ml-connector handles it

ml-connector stores IFS Cloud client credentials and Zendesk OAuth2 tokens encrypted and authenticates to IFS Cloud with the tenant-specific URL and OAuth2 bearer token. Because IFS Cloud is pull-only, it polls the OData SupplierSet and PostingProposalHeadSet (supplier invoices) on a schedule. Every IFS Cloud mutation operation requires the If-Match ETag header, so ml-connector reads the record first to capture its ETag before updating. Supplier data maps to Zendesk organizations by vendor ID, and invoice line items map to custom ticket fields. IFS Cloud enforces a 5000-element result set limit per request and rate limits at approximately 1000 requests per minute, so ml-connector uses pagination and exponential backoff with jitter on HTTP 429. Zendesk webhooks can be configured to push ticket updates back to trigger IFS Cloud GL posting or payment record changes. Every record carries a full audit trail.

A real-world example

A mid-sized manufacturing company runs IFS Cloud for procurement and finance and Zendesk for supplier support tickets. Before the integration, when a vendor submitted a support ticket about a delayed invoice or PO, the support team had no access to IFS Cloud payment status or invoice details and had to ask finance to look up the information, causing delays. With IFS Cloud and Zendesk connected, each new supplier ticket includes the vendor's open invoices, payment terms, and recent PO history automatically populated from IFS Cloud, so the support team can resolve payment disputes and order issues without leaving Zendesk.

What you can do

• •Sync IFS Cloud supplier invoices and vendor records into Zendesk organizations and custom ticket fields.
• •Capture payment status and invoice details from IFS Cloud and attach them to supplier support tickets in real time.
• •Bridge IFS Cloud OAuth2 and OData ETag concurrency requirements so your team does not need to manage both APIs.
• •Poll IFS Cloud on a schedule aligned with your accounts payable cycle, with automatic retry and exponential backoff on rate limits.
• •Replay failed Zendesk writes and maintain a complete audit trail of every synchronized record.

Questions

What data moves between IFS Cloud and Zendesk?

Supplier invoices and vendor records from IFS Cloud sync into Zendesk as organization records and custom ticket fields. Ticket resolution status can trigger reference updates in IFS Cloud if your process requires it. IFS Cloud is the source of truth for invoice amounts, payment status, and vendor contact details.

How does ml-connector handle IFS Cloud's ETag requirement and OData concurrency?

IFS Cloud requires the If-Match ETag header on mutations to enforce optimistic concurrency. ml-connector reads the record first to capture its ETag, then includes that ETag value on every update. This prevents lost-update race conditions when multiple systems or users change the same record simultaneously.

How does the integration work around IFS Cloud's lack of webhooks?

IFS Cloud offers no self-registering webhook API, so ml-connector polls the OData SupplierSet and PostingProposalHeadSet on a schedule tied to your accounts payable cycle. Zendesk webhooks can still notify ml-connector of ticket changes, allowing bidirectional awareness without waiting for polling intervals.