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, make sure you have:
1

Platform account

Active access with the right permissions on the target platform.
2

API credentials

Platform-specific keys or tokens required by the integration.
3

Telnyx AI assistant

A configured assistant ready to connect the integration.

​
Connection workflow

1

Open your assistant

Navigate to AI Assistants and open an existing assistant or create a new one.
2

Go to Integrations

Select the Integrations tab for that assistant.
3

Add a platform

Click Add Integration, choose a provider from the dropdown, and enter the required credentials.
4

Configure & save

Enable the tools you need, adjust defaults, and 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

Select your integration platform below. If you don’t see your platform, scroll horizontally to view all available options.
  • GitHub
  • Greenhouse
  • HubSpot
  • Intercom
  • Jira
  • Salesforce
  • ServiceNow
  • Zendesk

​
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

Generate a GitHub Personal Access Token at https://github.com/settings/tokens by clicking Generate new token → Generate new token (classic) and selecting scopes such as repo, read:user, and read:org, then copy the token (it only appears once).
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

Open your assistant

Navigate to the assistant you want to review in the Mission Control Portal.
2

Select Integrations

Open the Integrations tab.
3

Review Connected section

View everything listed 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

Open the assistant integration tab

Navigate to your assistant and open the Integrations tab.
2

Locate the integration

Find it within the Connected Integrations list.
3

Unassign

Click the chain-link unassign button.
4

Confirm

Approve the confirmation dialog to finish disconnecting.
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.
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

Open the Integrations tab

Navigate to your AI assistant and open the Integrations tab.
2

Find the integration

Look under Available Integrations.
3

Delete

Click the trash icon next to the integration.
4

Confirm

Approve the deletion to remove stored credentials permanently.
Jira integration card in Available Integrations showing connect button and delete button (trash icon)
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 profiles with only the permissions the workflow needs.
2

Rotate credentials regularly

Update API tokens and passwords on a routine cadence.
3

Monitor usage

Review integration activity through platform audit logs.
4

Limit permissions

Grant only the scopes required for each integration use case.
5

Use sandbox environments

Test and validate integrations in non-production environments first.

​
Configuration

1

Start with read-only tools

Enable search/read capabilities first, then gradually introduce write actions.
2

Provide clear descriptions

Document when and how each tool should be used so assistants respond correctly.
3

Test thoroughly

Validate integration behavior across multiple conversation scenarios.
4

Use tool parameters

Configure sensible defaults (e.g., priority, project) to reduce user input errors.
5

Handle errors gracefully

Define fallback behavior when integration calls fail or return unexpected results.

​
Performance

1

Minimize API calls

Avoid duplicate searches or redundant requests where possible.
2

Cache frequently accessed data

Store reusable values (for example, via dynamic variables) for the duration of a session.
3

Set appropriate timeouts

Configure timeout thresholds that balance responsiveness with reliability.
4

Monitor rate limits

Track provider limits and design workflows to stay within allocation.

​
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