Each tool connected to Guru has specific data (“objects”) that syncs with Guru, allowing you to search across tools and get answers directly in your workflow. Below is a breakdown of the objects synced from each source, along with more detailed information on source setup.
The flow for setting up a source is the same, but there are some nuanced differences depending on what type of tool you are looking to connect. As you follow the setup instructions, see here for any additional details.
| What you'll need | Objects we sync |
|---|
| Your team domain | Comments, Features, Products, Tasks, Users |
| What you'll need | Objects we sync |
|---|
| Airtable credentials | Specified tables |
| What you'll need | Objects we sync |
|---|
| Your Asana Credentials | Projects, Stories, Tasks, Users |
| What you'll need | Objects we sync |
|---|
| Your Basecamp subdomain | People, Projects, To Dos, Comments |
| What you'll need | Objects we sync |
|---|
| Your workspace ID | Issue, Repository, Comment, Member |
| What you'll need | Objects we sync |
|---|
| Select “Read Only” Permissions, Your Box Credentials | Files located in the specific folders you select |
| What you'll need | Objects we sync |
|---|
| Your Confluence credentials and read access to the space you want to sync | Page content for the designated space |
| What you'll need | Objects we sync |
|---|
| Your Clickup credentials | Comments, Spaces, Tasks, Teams, Groups, Users |
| What you'll need | Objects we sync |
|---|
| Dixa API Key | Conversation, Message, Agent, Note |
| What you'll need | Objects we sync |
|---|
| Your Dropbox Credentials | Files located in the specific folders you select |
| What you'll need | Objects we sync |
|---|
| FIle(s) stored locally | Most common file types supported |
| What you'll need | Objects we sync |
|---|
| Your Freshdesk subdomain | Agents, Companies, Conversations, Tickets, Replies, Notes |
| What you'll need | Objects we sync |
|---|
| Your Freshservice credentials | Ticket, Conversation, Agent |
| What you'll need | Objects we sync |
|---|
| Your Front credentials | Conversations, Inbox, Account, Message, Teammate, Event, Team |
| What you'll need | Objects we sync |
|---|
| Your Gitlab credentials | Issues, Projects, Comments, Users, Groups, Notes |
| What you'll need | Objects we sync |
|---|
| Your Gitlab credentials | Code Repositories |
| What you'll need | Objects we sync | Notes |
|---|
| Github username and fine-grained personal access token | Issues, Repositories, Comments, Users | The GitHub source allows Guru's GenAI search, Answers, to search across your Issues within GitHub and use the content in Issues to answer user questions. At this time, it does not include the ability to search across code repos or the GitHub wiki. Follow these instructions to generate a token which you'll need to use when setting up the source. |
| What you'll need | Objects we sync |
|---|
| Your Github credentials | Code Repositories |
| What you'll need | Objects we sync |
|---|
| Your Github credentials | Articles from designated GitHub wiki |
| What you'll need | Objects we sync |
|---|
| Your Gladly subdomain | Conversations, Tasks, Customers, Agents, Teams, Inboxes, Comments, Notes |
| What you'll need | Objects we sync | Notes |
|---|
Your Google Drive credentials. Inherited Permissions require an Admin scoped to drive.readonly, admin.directory.group.readonly, and
admin.directory.user.readonly | Files located in the specific folders you select | If using Inherited Permissions, users will only gain answers for the content they have access to in Google Drive |
| What you'll need | Objects we sync | Notes |
|---|
| Your Google Drive Credentials | Specific pages of sheets that you select | This will link existing live Google Sheets, not .xlsx files |
| What you'll need | Objects we sync |
|---|
| Your Gorgias subdomain | Tickets, Messages, Users, Teams |
| What you'll need | Objects we sync |
|---|
| Gong credentials | Gong Transcripts |
| What you'll need | Objects we sync |
|---|
| N/A | Articles from Guru's Help Center |
| What you'll need | Objects we sync |
|---|
| Help Scout credentials | Conversations, Mailboxes, Threads, Users, Teams, Members |
| What you'll need | Objects we sync |
|---|
| Hive API Key | Task, List, Activity, User, Group |
| What you'll need | Objects we sync |
|---|
- API Access
- Available in all Hubspot CRM editions per the Hubspot API documentation page [https://developers.hubspot.com/apisbytier]
- Access is controlled via a Private App defined in Hubspot
- Admins configure the Private App within Hubspot including all scopes and data access
- Guru utilizes the Private App via an API key provided in the integration installationNote: on the first screen in the setup process, you will need to input your Hubspot Tenant ID in the "Enter your CRM's subdomain" field. You can find your tenant ID in Hubspot in the dropdown on the upper right hand side (see below). | Companies (Accounts), Pipelines (Stages), Owners (Users), Deals (Opportunities), Notes, Tasks |
| What you'll need | Objects we sync |
|---|
- API Access
- Available in all Hubspot Service Hub editions per the Hubspot API documentation page
- Access is controlled via a Private App defined in Hubspot
- Admins configure the Private App within Hubspot including all scopes and data access
- Guru utilizes the Private App via an API key provided in the integration installation | Tickets |
| What you'll need | Objects we sync |
|---|
| Intercom Credentials | Companies, Conversations, Users |
| What you'll need | Objects we sync |
|---|
| Intercom Credentials | Articles |
| What you'll need | Objects we sync |
|---|
| Ironclad domain | Workflows, Users |
| What you'll need | Objects we sync |
|---|
| Jira domain | Projects, Issues, Users, Comments |
| What you'll need | Objects we sync |
|---|
| Jira subdomain | Projects, Issues, Comments, Users |
| What you'll need | Objects we sync |
|---|
| API Key | Conversations, Users, Companies, Notes, Messages |
| What you'll need | Objects we sync | Notes |
|---|
| Kustomer credentials | Articles | Install the Guru app within Kustomer instance before connecting Kustomer Knowledge Base |
| What you'll need | Objects we sync |
|---|
| Linear credentials | Tickets, Users |
| What you'll need | Objects we sync |
|---|
| monday.com credentials | Boards and Groups that you specify |
| What you'll need | Objects we sync |
|---|
| Notion credentials | Pages you specify |
| What you'll need | Objects we sync |
|---|
| - Read only permission - OneDrive credentials | Files located in the specific folders you select |
| What you'll need | Objects we sync |
|---|
| Pivotal API Token | Story, Project, Comment, Users, Epics, Memberships |
| What you'll need | Objects we sync |
|---|
| Rally API key | Artifact, Project, Conversation, Users, Iterations, Releases, Milestones |
| What you'll need | Objects we sync | Notes |
|---|
| ReadMe API key | Articles from your ReadMe Guide | Does not include API Reference docs. Please use File Upload to load your Swagger/OpenAPI spec |
| What you'll need | Objects we sync |
|---|
| Re:amaze subdomain | Conversations, Messages |
| What you'll need | Objects we sync |
|---|
- API Access
- Available in the following editions per Salesforce Help Page
- Enterprise Edition
- Unlimited Edition
- Developer Edition
- Performance Edition
- A valid Salesforce User with API Access enabled can be used to access the API, per the Salesforce Developer site | Account, Opportunity, Notes, Stages, Tasks, Users, Custom Objects |
| What you'll need | Objects we sync |
|---|
- API Access
- Available in the following editions per Salesforce Help Page
- Enterprise Edition
- Unlimited Edition
- Developer Edition
- Performance Edition
- A valid Salesforce User with API Access enabled can be used to access the API, per the Salesforce Developer site | Cases |
| What you'll need | Objects we sync |
|---|
| ServiceNow subdomain | Tasks, Customer Accounts, Journals, Users, Incidents, Cases, Requests, Problem |
| What you'll need | Objects we sync |
|---|
“Read only for non-admin users” permissions
Sharepoint credentials | Files located in the specific folders you select |
| What you'll need | Objects we sync |
|---|
| Shortcut API Key | Epics, Stories, Workflows, Iterations, Projects, Groups |
| What you'll need | Objects we sync | Notes |
|---|
| Slack credentials | Messages in designated channels from the last 90 days | Admins have option to set up inherited Slack permissions |
💡
Tip
Consider also turning on Suggested Answers in Slack, so your team can access all connected content in Guru within their workflow in Slack
| What you'll need | Objects we sync |
|---|
| Smartsheet credentials | Designated table - you’ll be prompted to select the title column |
| What you'll need | Objects we sync |
|---|
| Client id & Secret (from Spotdraft’s team) | Contracts, Notes, Users |
| What you'll need | Objects we sync |
|---|
| Teamwork subdomain | Tasks, Projects, Comments, People, Task Lists |
| What you'll need | Objects we sync |
|---|
| Trello credentials | Cards, Comments, Boards, Members, Organizations |
| What you'll need | Objects we sync |
|---|
| Username, password, and domain | Veeva Vault QualityDocs that meet the following criteria:
Lifecycle = ‘Draft to Effective Lifecycle’ AND Status = ‘Effective’
OR
Lifecycle = ‘Draft to Approved Lifecycle’ AND Status = ‘Approved’ |
| What you'll need | Objects we sync |
|---|
- Wrike subdomain
- API Access
- All editions of per Wrike's pricing page
- A valid user is required to access the API | Comments, Tasks, Folders, Accounts, Users, Groups |
| What you'll need | Objects we sync |
|---|
- Zendesk credentials
- API Access
- All editions per Zendesk Pricing page
- Any valid Zendesk user can access the API | Tickets, Users, Accounts, Comments |
| What you'll need | Objects we sync | Notes |
|---|
| Zendesk subdomain, Zendesk API Token | Articles from designated Zendesk guide | You can designate which brand and which languages (multi-select) you'd like to sync. |
| What you'll need | Objects we sync |
|---|
| Zoho credentials | Bugs, Projects, Comments, Users, Bugs |
| What you'll need | Objects we sync |
|---|
| Zoho credentials, Org ID | Tickets, Accounts, Comments, Agents, Teams, Conversations, Threads |
There are several factors that impact how quickly a source is established, including rate limits, time to sync the content, and the time required to index the content for search.
Rate limiting helps keep things running smoothly by managing how many requests a client can send in a certain time. This ensures fair access for everyone and helps maintain consistent, reliable performance.
The different tools Guru connects with have different rate limits,
- Ticketing: On average, 50 API calls are needed to process 1,000 ticket records.
- File Storage: The initial sync typically requires 1 API call per record, with 2 API calls for each updated record.
- CRMs: Depending on the tool, for example Hubspot requires 40 API calls per hour, and Salesforce requires approximately 1 API call per hour.
