How can we help?

CRM integration problems can occur during initial authorization, configuration, or execution of an operation that depends on the external CRM. A connection issue does not always indicate a Polyosync platform failure. The cause may involve the CRM provider, account permissions, credentials, external service availability, or an unsupported operation. Common causes 1. Incorrect external account The connection may have been authorized using an account that does not have access to the intended CRM organization or records. 2. Insufficient permissions The external account may lack permission to retrieve or modify the required information. 3. Expired or revoked authorization An access token or API credential may no longer be valid. 4. Incomplete configuration Some CRM integrations require additional settings after authorization. 5. Provider restrictions The CRM provider may impose API limits, access policies, or subscription requirements. 6. External service outage The CRM service may be temporarily unavailable. 7. Unsupported operation The integration may not support the specific CRM action required by the workflow. 8. Changes in CRM configuration Modified fields, permissions, account settings, or other provider-side changes may affect existing operations. How to troubleshoot Step 1: Confirm the CRM service is supported. Review the available integrations in your Polyosync workspace. Step 2: Verify the external account. Ensure that the intended CRM account and organization were used. Step 3: Review authorization. Check whether the provider has revoked access or requires renewed authorization. Step 4: Verify permissions. Confirm that the account has access to the relevant records and operations. Step 5: Check the configuration. Review any required account, organization, or resource settings. Step 6: Test a simple supported operation. Use a controlled scenario to determine whether the connection works for a basic operation. Step 7: Review available error details. If the problem occurs within a workflow, inspect the relevant execution information where available. Step 8: Check the CRM provider. Review the provider's service status and any relevant API restrictions. Step 9: Reconnect only when necessary. If authorization is invalid, use the supported reconnection process. Avoid repeatedly reconnecting without first checking the underlying cause. What if the CRM connects but no records appear? Verify record permissions, field visibility, account selection, and the specific retrieval operation. What if reading records works but updating them fails? The connection may have read access without the write permissions or functionality required for modification. What information should I provide to Support? Include: 1. The CRM provider's name. 2. The affected Polyosync workspace. 3. The operation you attempted. 4. The approximate time of the issue. 5. The error message, if available. 6. Whether the connection previously worked. 7. Any recent relevant configuration changes. Never include passwords, API keys, access tokens, or other secret credentials. Recommended approach Investigate the specific failed operation before changing permissions or recreating the connection. This helps identify the root cause without introducing unnecessary security risks.