How quickly do Issues appear after a Salesforce event?
Near real-time — Issues are typically created within seconds of the Salesforce record being created or updated.
What if the same Salesforce record triggers the integration more than once?
The integration checks for an existing ZenQMS Issue with the same Salesforce Record ID before creating anything. If one already exists, the record is skipped — no duplicates are created.
Can I map fields to later stages of the Issue?
Not currently. Only the first stage custom fields can be populated via this integration. Fields on subsequent stages cannot be set at the time of Issue creation.
What happens if there's an error processing a record?
Errors are handled per record. If one record fails, the integration continues processing the remaining records. All failed records are logged with error details in the integration execution logs.
Can I pause the integration?
Yes — you can pause or disable the integration instance at any time. While paused, Salesforce events will not be processed. Re-enable it whenever you are ready to resume.
How do I know if the integration is working?
Check the execution logs in the integration platform. Every event is logged with its outcome — created, skipped, or error — along with details for any failures.
Can I change the field mapping after setup?
Yes. New Issues created after the change will use the updated mapping. Existing Issues that were already created are not affected.
Can I use a filter to only trigger on specific changes?
Yes. The Filter Formula field on Page 2 accepts standard Salesforce formula syntax. For example, ISCHANGED(Status) will only trigger when the Status field changes, and Status = 'Closed' will only trigger for records with a Closed status.
What Salesforce permissions does the integration need?
A Connected App with OAuth 2.0 enabled and two scopes: Perform requests at any time and Manage user data via APIs. The authenticated Salesforce user must also have read access to the record type being monitored.
What ZenQMS API permissions are required?
The ZenQMS API token needs Read access to Users (for the default assignee picker) and Read/Write access to at least one Issue category (for creating Issues and reading custom field definitions).