How can we help?

After connecting an external service to Polyosync, it is important to verify that the integration is correctly authorized and capable of supporting the intended business operation. A successful authorization process does not necessarily guarantee that every integration operation will work. The connection may still require additional configuration, appropriate permissions, or access to specific external resources. Step 1: Review the integration configuration Open the relevant integration management area in your Polyosync workspace. Locate the external service and review any available connection status or configuration information. Step 2: Confirm the correct external account Verify that the integration was authorized using the intended external account, organization, or workspace. Connecting the wrong account can cause missing data or unexpected authorization problems. Step 3: Check the required permissions Determine whether the integration has the access necessary for its intended operation. An integration may connect successfully while lacking permission to retrieve or modify a particular resource. Step 4: Review additional configuration Some integrations require resource selections or other settings after authorization. Verify that any required configuration is complete. Step 5: Perform a low-risk test Where a supported test action is available, use it to confirm that the connection behaves as expected. For integrations that can modify external data, use a test record or another controlled scenario. Avoid testing with consequential business operations unless the behavior has been verified. Step 6: Check the result Determine whether the operation completed successfully and produced the expected outcome. Where available, review the relevant execution details or error information. Step 7: Verify the external system If the operation is expected to create, update, or retrieve information, confirm the result in the external service where appropriate. Step 8: Test the intended workflow If the integration will be used by an automation or AI-powered workflow, verify the complete operational sequence. A functioning connection is only one component of a functioning workflow. What if the integration appears connected but operations fail? Possible causes include: 1. Insufficient permissions. 2. Missing resource configuration. 3. Invalid or expired authorization. 4. External provider restrictions. 5. Unavailable external services. 6. Incorrect workflow configuration. 7. Unsupported operations. Investigate the specific error rather than repeatedly reconnecting without identifying the cause. How frequently should I verify integrations? Review important integrations after initial setup, authorization changes, or relevant configuration updates. Business-critical connections may require additional operational oversight. What does a successful test prove? A successful test confirms that a particular operation worked under the tested conditions. It does not guarantee that every possible operation will succeed or that the external provider will remain available. Recommended practice Verify both technical connectivity and the expected business result. This helps ensure that integrations are not merely connected, but useful and reliable within your actual business processes.