Setting up Dixa as a Source
Connecting Dixa makes it easy to bring your customer support ticket data into Guru's AI-powered Answers system. Learn how to connect your Dixa account and turn existing ticket information into searchable knowledge for your team.
Access Required
Guru Access: You need to be an Admin or Source Creator to set up Sources
Dixa Access: The authenticating user must have API Access in Dixa, which only includes Admins.
Setting up Dixa as a Source
- In Guru, go to Manage > Sources.
- Choose Dixa from the list of integrations.
- (Optional) Filter your ticket data by last modified date.
- Add your API Key, which you can find in your Dixa account, by navigating to Settings > Manage > Integrations. Click Configure API tokens. Click Add API token to add the API token. Give the token a name and click Save. Copy & paste the token value where prompted.
- Add a display name for the Source (optional) and click Connect Source.
- Assign which Guru Groups should have access to this content.
Objects synced from Dixa
Primary objects are the objects used to generate the search record.
Common Model / What You'll See During Setup | Objects/Data Brought In | Key Fields |
|---|---|---|
Ticket | Primary Object: Dixa conversations/cases | • Name • Status (Enum) • Ticket type • Contact (UUID) • Assignees (Array) • Completed at • Remote created at • Remote updated at • Remote ID • Remote data |
Comment | Conversation messages from end users | • HTML body • Contact (UUID) • Ticket (UUID) |
Comment | Internal notes on conversations | • Body • User (UUID) • Ticket (UUID) • Remote created at • Remote ID • Remote data |
User | Dixa agents/team members | • Name • Email address • Avatar • Remote ID • Remote data |
Permissions
- When you connect Dixa as a source in Guru, you'll permission that content in Guru. Learn more here.
- If someone is not provided with access in Guru to this source, they will not see Dixa results in searches or when chatting with Guru.
Updated about 1 month ago