If you’re running into trouble while setting up or using your connectors, use this guide to identify and resolve common errors.
"URL pattern doesn't match"
Issue: The connector is not appearing when you attempt to configure an action.
Troubleshooting steps:
Check syntax: Ensure your URL pattern uses proper regex syntax.
Escape characters: Verify that all dots are properly escaped (use \. instead of .).
Test your pattern: Run your pattern through a regex tester to confirm it behaves as expected.
Validate the URL: Confirm that the action's URL matches your defined pattern exactly.
"Authentication failed"
Issue: You receive a 401 or 403 error during a test connection or workflow action.
Troubleshooting steps:
Verify credentials: Double-check that your API key is correct and has not expired.
Confirm method: Ensure you are using the correct authentication method for the service.
Check headers: Confirm that header names are exact, keeping in mind that these are case-sensitive.
Review documentation: Consult the API provider’s documentation for specific authentication requirements.
Check for additional headers: Some APIs require specific headers such as User-Agent or Accept. Ensure these are included if required.
"SSL certificate verification failed"
Issue: The system cannot establish a connection to APIs using internal or self-signed certificates.
Troubleshooting steps:
Upload certificate: Ensure your CA certificate is uploaded in the connector configuration.
Verify format: Ensure the certificate file is in PEM format.
Include chain: If necessary, ensure you have included the entire certificate chain.
Contact IT: Reach out to your internal IT team to confirm you are using the correct CA certificate.
"OAuth callback failed"
Issue: The OAuth authorization process fails to complete.
Troubleshooting steps:
Verify redirect URI: Ensure the redirect URI is correctly registered with your OAuth provider.
Check for exact match: Confirm the redirect URI matches exactly, including the protocol (http/https) and port.
Validate client info: Double-check that your Client ID and Client Secret are accurate.
Check URLs: Verify that both the authorization and token URLs are correct.
Disable blockers: Ensure your browser popup blockers are not interfering with the authorization window.
Review scopes: Some providers require specific scopes; check that you have requested the necessary permissions.
"Token expired"
Issue: The OAuth connector stops functioning after a period of time.
Troubleshooting steps:
Check refresh token: Verify if your OAuth provider has issued a refresh token for your connection.
Verify permissions: Ensure the connector has the necessary permissions to refresh tokens automatically.
Re-authorize: If the connection has lapsed, try re-authorizing the connector.
Check provider policies: Some providers require periodic manual re-authentication by design.