Integrations

The Integrations page (/admin/integrations) connects nara to external systems. Providers are grouped by domain: Communication, Knowledge base, Productivity, and Ticketing. Only one integration per domain is allowed — connecting a provider blocks the others in the same domain until it is disconnected.

Connecting a provider

1. Pick a provider card and click Connect.
2. Enter credentials for the provider’s authentication method:
   • OAuth — sign in and grant access in the provider’s consent flow.
   • Client Credentials — enter Client ID, Client Secret, and Tenant ID.
   • API Token — enter the token plus the Base URL and Username/Email.
3. Save. The integration switches to Active and the first sync starts.

An integration shows one of three statuses: Active, Disabled, or Error. Use Re-sync to trigger a fresh synchronization, and Disconnect to remove the integration.

Webhooks

Providers that push changes to nara register a webhook during setup. From the integration you can Rotate secret to invalidate the current webhook secret and Retry setup if webhook registration failed. Confluence Cloud does not support the required webhooks, so nara falls back to polling for it.

Local hosting

If a provider is only reachable inside your network, enable the Local hosting toggle to route all provider traffic through an online Edge deployment. The deployment must be online for syncs to run.

Outbound sync

The Outbound sync toggle controls whether changes made in nara (for example ticket updates) are written back to the provider. Disable it to run the integration read-only.

Provider notes

ServiceNow

Syncs incidents, requests, and catalog tasks. The integration surfaces per-table sync health, supports a dry run to preview changes without writing, and offers a backfill to import historical records.

Zammad

Ticketing integration connected via API token; tickets sync in both directions when outbound sync is enabled.

Confluence

Knowledge-base integration; pages are ingested into memory. Confluence Cloud uses polling instead of webhooks (see above).

Microsoft Teams

1. Package download — download the nara Teams app package.
2. Authorize — grant admin consent for the required Microsoft permissions.
3. Publish to catalog — upload the package to your organization’s Teams app catalog.
4. Select the Default Teams agent that answers conversations coming from Teams.

Microsoft Graph / SharePoint / Calendar

Connects Microsoft 365 for SharePoint knowledge sync, calendar access, and directory sync. The availability preview runs a mailbox Free/Busy check so you can verify calendar access before agents rely on it.

Jira

Ticketing integration for Jira issues.

Zendesk

Ticketing integration for Zendesk tickets.

Note

Tools that depend on an integration appear in the Available Integrations panel of the tool editor; they only work while the integration is Active.