Skip to main content

AI assistant integrations

Telnyx AI assistants can integrate with leading enterprise platforms to access customer data, create tickets, update records, and automate workflows directly during conversations.

Available integrations ​

IntegrationDescriptionCommon Use Cases
SalesforceCRM platform for sales, service, and marketingLead qualification, case management, contact updates
ServiceNowIT service management and workflow automationIncident creation, ticket updates, service requests
JiraProject management and issue trackingBug reporting, task creation, project updates
HubSpotMarketing, sales, and service CRMContact management, deal tracking, ticket creation
ZendeskCustomer service and support platformTicket creation, customer lookup, case management
IntercomCustomer messaging and support platformConversation management, user data access
GitHubCode hosting and version controlIssue creation, repository access, pull request management
GreenhouseApplicant tracking and recruiting platformCandidate lookup, interview scheduling, application management

Getting started ​

Prerequisites ​

Before connecting an integration, ensure you have:

  1. Platform Account - Active account with appropriate permissions on the target platform.
  2. API Credentials - Platform-specific credentials (varies by integration).
  3. Telnyx AI Assistant - A configured AI assistant ready to connect.

Connection workflow ​

  1. Navigate to AI Assistants in the Mission Control Portal.
  2. Click on an existing assistant or create a new one.
  3. Go to the Agent tab.
  4. Scroll to the Integrations section.
  5. Click Add Integration.
  6. Select the platform from the dropdown menu.
  7. Enter the required credentials.
  8. Configure available tools.
  9. Save the assistant.

Mission Control Portal showing Add Integration dropdown with available platforms including GitHub, Greenhouse, HubSpot, Intercom, Jira, Salesforce, and Zendesk

See integrations in action ​

Watch how Telnyx Voice AI Agents connect to enterprise platforms like ServiceNow to create, update, and resolve tickets through natural voice conversation:

This demonstration shows the integration workflow in the Mission Control Portal and real-time ticket management capabilities that work across all supported platforms.

Platform-specific setup ​

note

Select your integration platform below. If you don't see your platform, scroll horizontally to view all available options.

GitHub ​

Connect your AI assistant to GitHub for code hosting, version control, and development workflows.

Prerequisites ​

  • GitHub account with repository access.
  • Permissions to create personal access tokens.
  • Appropriate repository scopes for integration needs.

Required credentials ​

When connecting GitHub, you'll need to provide:

  1. Access token - Your GitHub Personal Access Token.
    • Create one at: https://github.com/settings/tokens
    • Click "Generate new token" → "Generate new token (classic)"
    • Select appropriate scopes:
      • repo - Full control of private repositories
      • read:user - Read user profile data
      • read:org - Read organization data
    • Copy the generated token (you won't be able to see it again)

GitHub integration credentials dialog showing Personal Access Token input field

Available tools ​

After connecting GitHub, your assistant can:

  • Create issues - Log bugs, feature requests, or tasks in repositories.
  • Search repositories - Find repos by name, description, or topics.
  • Manage pull requests - Create, review, or update PRs.
  • Access code - Read file contents and repository structure.
  • Manage labels - Add or remove issue and PR labels.

Use cases ​

Bug Reporting

Developer: "We have a login bug affecting Safari users"
Assistant: [Creates issue in GitHub repository]
Assistant: [Adds labels: bug, priority:high, browser:safari]
Assistant: "I've created issue #234 in the main repo and notified the team."

Repository Search

Developer: "Find our authentication libraries"
Assistant: [Searches GitHub repos by keyword and topic]
Assistant: "I found 3 authentication repos: auth-service, jwt-utils, and oauth-client."

Managing integrations ​

Viewing connected integrations ​

  1. Navigate to your AI assistant in the portal.
  2. Go to the Agent tab.
  3. Scroll to the Integrations section.
  4. Connected integrations appear under Connected Integrations.

Integrations section displaying Jira under Connected Integrations with description and unassign button

Disconnecting an integration ​

To disconnect an integration from your assistant:

  1. Navigate to your AI assistant in the portal and go to the Agent tab.
  2. Scroll to the Integrations section.
  3. Find the integration in the Connected Integrations list.
  4. Click the unassign button (chain link icon) next to the integration.
  5. In the confirmation dialog, click Continue to confirm disconnection.

Jira integration card in Connected Integrations showing unassign button (chain link icon)

After disconnecting:

  • The integration is removed from this assistant.
  • All associated tools are disabled for this assistant.
  • The integration moves to Available Integrations and can be reconnected later.
note

Disconnecting an integration only removes it from the current assistant. The integration remains in your account and can be connected to other assistants or reconnected to this one.

Deleting an integration ​

To permanently delete an integration from your account:

  1. Navigate to your AI assistant in the portal and go to the Agent tab.
  2. Scroll to the Integrations section.
  3. Find the integration in the Available Integrations list.
  4. Click the delete button (trash icon) next to the integration.
  5. Confirm deletion.

Jira integration card in Available Integrations showing connect button and delete button (trash icon)

warning

Deleting an integration permanently removes it from your account, including all stored credentials. You will need to set it up again from scratch if you want to use it in the future.

Best practices ​

Security ​

  1. Use dedicated service accounts - Create integration-specific accounts with minimal required permissions.
  2. Rotate credentials regularly - Update API tokens and passwords periodically.
  3. Monitor usage - Review integration activity in platform audit logs.
  4. Limit permissions - Grant only the permissions needed for specific use cases.
  5. Use sandbox environments - Test integrations in sandbox/staging before production.

Configuration ​

  1. Start with read-only tools - Enable search/read tools first, then add write capabilities.
  2. Provide clear descriptions - Help the assistant understand when to use each tool.
  3. Test thoroughly - Validate integration behavior with various conversation scenarios.
  4. Use tool parameters - Configure defaults to reduce errors (e.g., default priority, project).
  5. Handle errors gracefully - Configure fallback behavior when integration calls fail.

Performance ​

  1. Minimize API calls - Avoid unnecessary searches or duplicate requests.
  2. Cache frequently accessed data - Use dynamic variables for session-specific data.
  3. Set appropriate timeouts - Configure reasonable timeout values for integration calls.
  4. Monitor rate limits - Be aware of platform-specific API rate limits.

Troubleshooting ​

Connection failures ​

Symptom: Unable to connect integration, credentials rejected.

Solutions:

  • Verify credentials are correct and have not expired.
  • Check that the user account has API access enabled.
  • Ensure security tokens or API keys are current.
  • For Salesforce: Confirm security token is included.
  • For cloud platforms: Verify instance URL format (no https:// or trailing /).

Tools not appearing ​

Symptom: Integration connected but no tools available.

Solutions:

  • Refresh the page and check again.
  • Verify the integration account has required permissions.
  • Check that the platform subscription includes API access.
  • Disconnect and reconnect the integration.

Authentication errors during calls ​

Symptom: Tools fail with authentication errors during conversations.

Solutions:

  • Regenerate API tokens or security tokens.
  • Update stored credentials in the integration.
  • Verify account has not been locked or suspended.
  • Check IP allowlists (if applicable).

Missing data or records ​

Symptom: Assistant cannot find expected records.

Solutions:

  • Verify the integration account can access the records.
  • Check record permissions and sharing settings.
  • Confirm records exist in the platform.
  • Verify search parameters and filters.

Rate limiting ​

Symptom: Integration calls fail with rate limit errors.

Solutions:

  • Reduce frequency of integration calls.
  • Implement caching for frequently accessed data.
  • Contact platform support to increase limits.
  • Distribute calls across multiple service accounts.

Next steps ​