Setting up Vitally as a Source
Access RequiredGuru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.
Vitally Access: The authenticating user must be a Vitally Admin. Only Admins can enable the REST API and generate API keys in Vitally. All Vitally plans (Tech-Touch, Hybrid-Touch, and High-Touch) include API access and are supported.
Setting up Vitally as a Source
- In Guru, go to Apps and Integrations.
- Select Sources, then click Add Source.
- Choose Vitally from the list of integrations.
- Enter your Vitally API key to authenticate.
- Filter data to start pulling content in from a specific start date (optional).
- Add a display name for the Source (optional) and click Connect Source.
- Assign which Guru Groups should have access to this content.
Note:
To generate an API key in Vitally, a Vitally Admin must first enable the REST API in Vitally's settings. The API key has full read/write access in Vitally, but Guru only performs read operations. Vitally does not support granular API key scoping.
Objects synced from Vitally
Guru syncs customer success data from your Vitally workspace to power Answers. This content does not appear as Cards in Guru and is not directly searchable, but will be cited in generated Answers.
Organizations
| Identity | Metrics | Usage | Metadata |
|---|---|---|---|
| Name | MRR | Users count | Created date |
| External ID | Health score | Accounts count | Last updated |
| NPS score | Traits | URL |
Accounts
| Identity | Metrics | Lifecycle | Metadata |
|---|---|---|---|
| Name | MRR | Next renewal date | Created date |
| External ID | Health score | Churned date | Last updated |
| Organization ID | NPS score | First seen timestamp | URL |
| Users count | Last seen timestamp | ||
| Traits |
Notes
| Content | Context | Author | Metadata |
|---|---|---|---|
| Subject | Account name | Author name | Note date |
| Note body | Organization name | Author ID | Created date |
| Category name | Last updated | ||
| URL |
Tasks
| Details | Context | Assignment | Metadata |
|---|---|---|---|
| Name | Account name | Assigned to (name) | Due date |
| Description | Organization name | Assigned to (ID) | Completed date |
| Category ID | Created date | ||
| Last updated | |||
| URL |
Projects
| Details | Context | Owner | Dates |
|---|---|---|---|
| Name | Account name | Owner name | Target start / completion |
| Status name | Organization name | Owner ID | Actual start / completion |
| Category name | Created date | ||
| Last updated | |||
| URL |
Permissions
When you connect Aha! 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 Aha! results in searches or when chatting with Guru.
Updated about 2 hours ago