Automate Client Sync Between SI and Third-Party Integrations

The SI API supports publishing and subscribing to Clients, but Client workflows still require manual user steps inside SI.

Today, when a third-party system publishes a new client through Publish/Clients, the client appears in Import Client from Integration(s) and requires a user to manually import it before it exists in SI.

In the opposite direction, SI clients are not automatically made available to the API when they are created or updated in SI. A user must manually select/export clients to the integration before they become available through the Client Subscribe API and before the Client webhook is triggered.

This makes true two-way Client synchronization difficult for integrations where another system is the CRM or customer master.

Requested functionality

Please add Client automation options similar to the existing Project and Catalog automations:

• Automatically import/create new Clients in SI when they are received through Publish/Clients.

• Automatically apply Client updates received through Publish/Clients/Update.

• Automatically publish/export Clients to the API when they are created or updated in SI.

• Trigger the Client webhook automatically on Client create/update/delete events in SI, without requiring a user to manually Export the Client first.

• Preserve a durable integration identifier so external systems can reliably correlate the SI Client UUID with the external customer ID.

Suggested controls

These could be configurable under Manage Integration Settings, for example:

• Create Clients from Integration: Yes/No

• Update Clients from Integration: Yes/No

• Publish Client Creates to Integration: Yes/No

• Publish Client Updates to Integration: Yes/No

• Publish Client Deletes to Integration: Yes/No

Why this matters

Many companies use another platform as their CRM or operational customer database.

We need Client identity, addresses, contacts, and updates to stay synchronized without requiring employees to manually Import or Export Clients in SI.

The current manual dependency creates several risks:

• new clients can sit waiting in the integration queue unnoticed

• users can accidentally import a duplicate of an existing SI client

• client UUIDs cannot be written back to the external system until the manual SI step occurs

• changes can remain stale until someone remembers to export the client

Expected workflow

External system creates/updates Client → SI automatically consumes it → SI Client UUID is available to the integration.

SI user creates/updates Client → SI automatically publishes it to the integration → Client webhook fires → external system can reconcile immediately.

This would allow the existing Client API to support a truly unattended two-way Client synchronization workflow.

We have already built and tested this using the existing SI Client API, and the only remaining limitation is the required manual Import/Export step inside SI.