Integrations

Integrations Configuration

What are integrations?

Integrations connect nara to external tools and services your organization already uses. Once connected, agents can interact with these systems directly — searching knowledge bases, creating tickets, syncing data, and more — without leaving the nara platform.

Each integration establishes a secure connection to a third-party provider and makes provider-specific tools available to your agents.

Available providers

nara supports integrations with the following providers:

Provider	Domain	Description
Jira	Ticketing	Create, search, and manage Jira issues and projects
Confluence	Knowledge base	Search and retrieve Confluence pages and spaces
Azure DevOps	Ticketing	Manage work items, boards, and sprints in Azure DevOps

Note

The list of supported providers is continuously expanding. Contact your account manager for information about upcoming integrations.

Integration domains

Integrations are grouped by their functional domain:

Ticketing systems

Connect to external ticketing platforms to create, search, and manage issues. Agents can file tickets in your external system alongside nara’s built-in ticket management.

Knowledge base systems

Connect to knowledge repositories so agents can search articles, retrieve documentation, and reference external content during support conversations.

Authentication types

Different providers support different authentication methods. Choose the method that matches your provider’s requirements and your organization’s security policies.

API Token

API token authentication uses a key or token that you generate in the external provider’s settings. This method is straightforward and suitable for providers that support personal access tokens or API keys.

Required credentials:

• API Token — the token or key generated by the provider.
• Base URL — the provider’s API endpoint (e.g., https://your-domain.atlassian.net).
• Username or email — required by some providers to pair with the token.

Tip

Use a service account rather than a personal account for API tokens in production. This avoids disruption if a team member leaves the organization.

OAuth 2.0

OAuth 2.0 authentication uses the authorization code flow with a callback URL. This method is more secure for production use and avoids storing long-lived tokens.

How the OAuth flow works:

1. nara redirects you to the provider’s authorization page.

2. You log in to the provider and grant nara the requested permissions.

3. The provider redirects back to nara’s callback URL with an authorization code.

4. nara exchanges the code for access and refresh tokens.

5. Tokens are stored securely and refreshed automatically when they expire.

OAuth connections require that your provider’s admin has registered nara as an authorized application.

Connecting an integration

1. Select provider — navigate to Settings > Integrations and choose the provider you want to connect (e.g., Jira, Confluence, Azure DevOps).

2. Choose auth method — select either API Token or OAuth 2.0, depending on what the provider supports and your preference.

3. Provide credentials — enter the required credentials for your chosen authentication method. For API Token, supply the token and base URL. For OAuth, initiate the authorization flow.

4. Test connection — nara validates the credentials by making a test request to the provider’s API. If the test fails, check your credentials and try again.

5. Activate — once the connection test passes, activate the integration. It is now available for use by agents and tools.

Managing active connections

After connecting an integration, you can manage it from the Settings > Integrations page:

• View status — see whether each integration is ACTIVE, DISABLED, or in an ERROR state.
• Refresh credentials — for OAuth connections, manually trigger a token refresh if needed.
• Update configuration — modify the base URL, credentials, or other settings.
• View connected tools — see which tools are using this integration connection.

Connection statuses

Status	Description
ACTIVE	The integration is connected and working. Tools can use this connection to interact with the provider.
DISABLED	The integration has been manually deactivated. Tools will not use this connection until it is re-enabled.
ERROR	The connection encountered an issue (e.g., expired credentials, provider API unreachable). Review and fix the configuration to restore the connection.

Disconnecting integrations

To disconnect an integration:

1. Navigate to Settings > Integrations.

2. Find the integration you want to disconnect.

3. Click Disconnect and confirm.

4. The connection is removed and any tools that depended on it will no longer have access to the provider.

Caution

Disconnecting an integration immediately revokes access. Agents will no longer be able to use tools that require this connection. Make sure no critical workflows depend on the integration before disconnecting.

Tool integrations

Connected integrations enable provider-specific tools that agents can invoke during conversations. Examples include:

Tool	Provider	Description
searchProviderArticles	Confluence	Search for articles in connected knowledge bases
getProviderArticle	Confluence	Retrieve a specific article by ID
searchProviderTickets	Jira / Azure DevOps	Search for tickets or work items in the connected system
createProviderTicket	Jira / Azure DevOps	Create a new ticket or work item in the external system

These tools appear automatically in the tool registry once the corresponding integration is active. Assign them to agents through the agent configuration page.

Next steps

Tool Management Manage and assign tools that use integration connections.

Managing Agents Assign integration-powered tools to your agents.

Organization Manage organization settings and members.