Salesforce Integrations

You can use this integration if your main ITSM/CRM system is Salesforce and you want to sync tickets from the teams who use ServiceNow. The opposite is also possible.

When a case is created in Salesforce, ZigiOps will collect it instantly and create a related Incident/Change Request in ServiceNow.

You have a high degree of control over data filtering to make sure the platform collects only the required Salesforce Cases. You also have full control of the data field mapping, allowing you to define how ZigiOps reports data to ServiceNow. Regular fields, custom fields, lifecycle fields, comments, and attachments are part of the synchronization.

Updates in Salesforce for Cases already transferred to ServiceNow are collected and synchronized with the related Incident/Change in ServiceNow for regular fields, custom fields, lifecycle fields, comments, and attachments.

ZigiOps collects updates from ServiceNow for the Incidents/Changes that were created as Cases in Salesforce. It syncs them with the related Cases in Salesforce for regular fields, custom fields, lifecycle fields, comments, and attachments.

If one of the systems you are using is Salesforce and you want to transfer cases to DevOps teams, who use Jira, you can use the ZigiOps integration platform.

Our integration between Salesforce and Jira is bi-directional, which means that once there is an update in one of the systems, the other automatically receive it as well. For example, when a case is created in Salesforce, the integration platform will pull it automatically and create a related issue in Jira. You have a high degree of data filtering control, so the platform collects only the required Salesforce cases. You also have full control over data field mapping to define how ZigiOps reports data to Jira. You can synchronize regular and custom fields, lifecycle fields, issue links, comments, attachments, and more.

ZigiOps automatically collects any updates in Salesforce and transfers them to Jira by filling all the necessary fields in the ticket. Similarly, it collects updates from Jira and updates them in Salesforce. The integration platform synchronizes them with the related case in Salesforce for regular fields, custom fields, lifecycle fields, issue links, comments, and attachments.

Your team uses Salesforce as the main CRM system. They need, however, to sync Cases with the teams who use Cherwell. In such a scenario, ZigiOps steps in and handles the integration between the two software tools to achieve it. In cases when the main ITSM system happens to be Cherwell, aligning with the teams that use Salesforce is also possible.

A Case is created in Cherwell. ZigiOps steps in and picks it up. This happens at a pre-defined interval. Once ZigiOps fetches the Case, it then creates a related Incident/Change in Cherwell’s system. Thanks to the fact that there is control on data filtering, ZigiOps collects only the required Salesforce Cases. The same is valid for field mapping, which defines how ZigiOps reports data to Cherwell. Regular fields, custom fields, lifecycle fields, and comments are all included in the synchronization process between the two systems.

Salesforce’s updates that refer to the Cases already transferred to Cherwell are also collected at a scheduled interval. They are synchronized with the related Incident/Change in Cherwell for regular fields, custom fields, lifecycle fields, and comments.

Updates in Cherwell for Incidents/Changes created in Salesforce are also collected at a pre-defined interval and are synchronized with the related Case in Salesforce for regular fields, custom fields, lifecycle fields, and comments.