Troubleshoot integrations – Tekst

This guide will aid in solving common issues when trying to connect to an integration on Tekst.

Symptoms: Errors like "No code" or "Failed to get access token" appear after authorization.

Solution:

Click the Retry button to restart the authorization flow
Verify that Tekst's redirect URI is whitelisted in your provider's app registration (e.g., Azure AD for Outlook, Salesforce Connected App)
Ensure you're granting all required scopes during authorization

Symptoms: Message stating "This connection already exists in another org" or "Inbox connected to another org."

Solution:

Switch to the correct organization where the connection was originally created
If you need to move the connection, ask an admin to disconnect it from the original org first

Symptoms: "Authentication failed" for username/password integrations, or "API limit exceeded" for providers like Salesforce.

Solution:

Reconnect the integration and verify credentials are correct
For API limits, use a dedicated integration user with appropriate OAuth client credentials (recommended for high-volume environments)
Wait for rate limits to reset, or contact your provider to increase limits

Symptoms: Unable to proceed to the next step in the setup wizard.

Solution:

Complete all required fields in the current step before clicking Next
If you edited a previous step, re-enter information in subsequent steps as they were reset

If you encounter permission-related errors, contact your organization admin to update your permissions.

Symptoms: Integration requests from Tekst fail to reach your service, webhook deliveries time out, or custom step calls are rejected.

Solution:

Tekst uses fixed IP addresses for all outbound communication. If your firewall or service restricts incoming traffic by IP, add Tekst's outbound IP addresses to your allow list
See Troubleshoot Firewall for the full list of IP addresses to whitelist

Related articles