Connectors overview
Every app you can connect to Gurusup, what each one reads, and the rules all connectors share, from approval to disconnecting.
Read this before you connect your first app, then go to that app's page for the steps. Admins connect sources. Members can open Sources and Catalog to read about company sources, and they can upload files, but they cannot connect or manage company sources. The exception is tl;dv: each person can connect their own key while an admin lets members do so.
A connector is an app you link to Gurusup so it learns from what your team already writes there. Each connected app feeds one or more sources, and a source is anything that feeds Brain. For the bigger picture, see How Brain works.
What you can connect
Gurusup is most useful when it can join several tools: a question like "Why did the Acme renewal slip?" needs the Slack thread, the HubSpot deal and the Linear issue together.
| Kind of tool | Connector | What Gurusup reads | Stays up to date |
|---|---|---|---|
| Chat | Slack | Messages and the contents of shared files in the channels and group messages the app joins, from its notice on | As messages arrive |
| Meetings | HappyScribe | Each finished meeting: summary, action items, transcript | When a meeting finishes |
| Meetings | Granola | Each meeting note: notes, summary, transcript | When Granola finishes a note |
| Meetings | tl;dv | Each meeting with a finished transcript: details, notes, transcript | About every 15 minutes |
| Docs and wikis | Notion | The pages you share, with their properties | As pages change |
| Docs and wikis | Mintlify | Each public page of your docs that changes after you connect, up to 2,000 | Every 6 hours |
| Docs and wikis | Documentation.AI | Each public page of your docs that changes after you connect, up to 2,000 | Every 6 hours |
| CRM | HubSpot | Deals, with their contacts, companies and activity | When a deal changes |
| CRM | Attio | Companies, deals and custom objects, with people, lists, notes, tasks, comments and meetings | Within minutes |
| Projects and issues | Linear | Public issues, projects, initiatives, cycles, documents, releases and customers | On every change |
| Projects and issues | ClickUp | Tasks in spaces shared with the whole workspace | Within minutes |
| Projects and issues | Asana | Projects and tasks shared with the whole workspace | On every change |
| Projects and issues | monday.com | Public boards and their items | Within minutes |
| Finance | Holded | Documents your token can read, plus contacts, products and services | Within minutes, or every 6 hours for some types |
| Human resources | Factorial | The company, people and finance types you choose, such as announcements, policies and documents | Every hour, 30 minutes or 6 hours, by type |
| Human resources | Sesame | Company structure, time-off rules and, if you choose, who is out | Every 30 minutes or 6 hours |
| Marketing | Zernio | Posts, blog articles, reviews, comments and ad campaigns, as you choose | Every 6 hours, or every day for blogs and ads |
| Your own tools | Webhook | Any JSON object your tool sends, and files you add by hand | Whenever your tool sends data |
| Your own files | Upload files | The files you drop in | No. Gurusup reads them once. |
What each app leaves out, and the exact permissions it asks for, are on its page.
Who can connect what
| You are | What you can do |
|---|---|
| An admin | On Sources, use Upload files, Import wiki and Connect source, and Add webhook source in Catalog. On a source's page, admins can connect, choose who reads the source, import past content, reconnect, remove and disconnect. |
| A member | Open Sources and Catalog, and read the Company sources table, which lists only the sources they can read. Source rows open the source's page. In Catalog, search the sources or browse them by category: each row has a View button or a Connected mark. On Sources a member can also use Upload files and Import wiki. Members cannot connect or manage company sources: on an app's page, Connect for the organization is off with the hint "Only administrators can connect organization accounts." Members can connect their own tl;dv key while an admin lets members connect their own account: see Connect tl;dv. |
You also need an account in the app itself that can approve access or create a key. Each connector's page says which one.
Every connection belongs to the organization
When an admin connects an app, the connection belongs to your organization, not to that admin. What Gurusup learns goes into the organization's memory, and people read it according to its knowledge access. Disconnecting is also an admin action, for the whole organization.
tl;dv takes two kinds of connection. Admins always connect it for the organization, like any other connector. Each person can also connect their own key while an admin keeps Let members connect their own account on. It starts as Private, and an admin can disconnect it but not open it. See Connect tl;dv.
Gmail and Google Drive are personal connections behind a feature flag and are not covered here. Watch for keys that reach private content: a Granola personal key brings that person's private notes in as an organization source, so restrict it when you connect it.
How you connect each app
| How | Apps | What you do |
|---|---|---|
| Approve in the app | Slack, Notion, HubSpot, Linear | On the app's page, click Connect for the organization, then Connect in the dialog, approve in the app and come back. See How approval works. |
| Paste a key or token | HappyScribe, Holded, ClickUp, Asana, Granola, tl;dv, Factorial, Sesame, Zernio, monday.com, Attio | Create the key in the app and paste it in the connect dialog. The hint under the field and Show steps say how. For tl;dv, a person can paste their own key. |
| Paste an address | Mintlify, Documentation.AI | Paste the public address of your docs. No account needed. |
| Use a URL | Webhook | Gurusup gives you a URL and your tool sends data to it. |
For every key or address except HappyScribe, Connect stays off until Gurusup has checked what the key reaches, and the dialog shows it first: the spaces, projects, boards or folders it will read. If something is wrong, a red message starts with "Could not connect" and the app's name, then the reason. Each connector's page lists its messages.
How approval works
Slack, Notion, HubSpot and Linear connect through the app's own approval screen.
Open the app
In the sidebar, open Sources, then Catalog. Find the app (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect (App) for the organization opens.
Choose who reads it
Optional. In the dialog, under Who can read it, choose Default access, Restricted or Private from Access mode. See Who reads what a connector brings in.
Approve in the app
Click Connect in the dialog. Gurusup says "Opening authorization for" the app and sends you there. Approve the access it asks for.
Come back to Gurusup
The app sends you back to the page you started from, or to Sources if your browser no longer remembers which page that was, and a message such as "Notion connected." appears. Slack opens a dialog first, Finish setting up Slack, and the message appears when you click Done: see Connect Slack. If it failed, you land in the same place, a red message says why, and nothing is connected.
The approval link expires after 15 minutes. After that Gurusup says "OAuth state expired. Start the connection again." Using the same link twice gives "This connection request was not found or was already used. Start the connection again." In both cases, start again from Catalog. Other messages are in Connector troubleshooting.
The same account in several organizations
One Slack workspace, Notion workspace, HubSpot account, Linear workspace or HappyScribe workspace can be connected to more than one Gurusup organization. Each organization approves it on its own, and nothing is shared between them: credentials, sources, what Gurusup learns, who can read it and the ingestion status stay in each organization. Changes in the app reach every connected organization separately. Inside one organization, connecting the same account again reconnects the existing connection instead of adding a second one.
Who reads what a connector brings in
Each source has a knowledge access setting:
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
Under Knowledge access on a source's page, and under Who can read it in the connect dialog, Default access reads "Everyone reads it according to what they are already allowed to see." Restricted reads "Only the people you choose. Administrators only if you choose them." Private reads "Only you. Administrators can't read it either."
When you connect from Sources, the connect dialog asks Who can read it with an Access row and an Access mode menu (Default access, Restricted or Private), and says "Gurusup applies this from the first item it reads." For Slack, every channel the app joins later starts with that access. Sources with no connection, such as a webhook or Local Uploads, have the same Knowledge access section on their page. You can change it there at any time: it saves as soon as you change it ("Knowledge access saved."). Going from Restricted back to Default access asks "Switch to default access" first, with Cancel and Confirm.
| Situation | What happens |
|---|---|
| You connect during setup, or on Home before the first build | No choice: the source starts with Default access. |
| You restrict a source later | It only covers what comes next. Gurusup says "Restricting this source applies to future ingestions. Knowledge Gurusup already has keeps its existing category permissions." |
| The app has its own permissions | Gurusup does not copy them. Who sees a Slack channel or a Notion page does not limit who reads it in Gurusup. |
If a source must be private from the start, restrict it when you connect it. The full guide is Restrict a source to specific people.
How connectors keep Gurusup in sync
Connecting is not a one-time copy. Gurusup picks up new and changed content on its own, at the speed shown in What you can connect. You do not reconnect or reshare.
| Question | Answer |
|---|---|
| Where does Gurusup start? | From now. Slack reads messages posted after the app's notice in a channel. Notion and HubSpot read what changes after you connect. HappyScribe reads meetings that finish after you connect. Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Zernio, monday.com and Attio start when you connect, and History says "Only new content comes in until you import past content." Sesame starts when you connect too and has nothing to import. Mintlify and Documentation.AI check your docs when you connect but only learn the pages that change after that, and check again every 6 hours. |
| When does the first read start? | Right away. On Follow ingestion the first items show Queued, then Learning. |
| How do existing Notion pages and HubSpot deals come in? | Gurusup does not walk everything when you connect, in setup or outside it. Use Import history for pages edited, or deals with activity, in a window. For Notion you can also tick pages with the page picker under Content and click Import selected while an import is running (without one it adds nothing), or upload an export. |
| What has no past content at all? | Slack history, Sesame, and HappyScribe meetings that finished before you connected. A source you connect through an assistant never imports history either: older history is a separate step you agree to. |
| Does it use my usage? | Yes, like an upload. When usage runs out, a banner says so, new items show Paused on Follow ingestion, and they resume by themselves when usage renews or increases. See Usage and limits. |
Import history
HubSpot, Notion, Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Zernio, monday.com and Attio bring in past content with Import history.
Open Import history
On Sources, open the source's page. Under History, click Import history.
Pick how far back
Pick Last week, Last month, Last 3 months, Last 6 months or Last year. Gurusup shows what it found in that window and, when it can tell, what the import would use out of what you have left this month.
Import
Click Import. Gurusup says "Importing history. It keeps going in the background."
If it costs more than you have left, what does not fit waits and comes in when your usage renews. If the import stops, the row says "The import didn't finish. Try again, and contact support if it keeps failing." and the button reads Try again.
Everything a connector reads then goes through the same steps as any other source. Follow it on Follow ingestion and check each source on Check source status.
More than one account
| App | How to add another |
|---|---|
| Slack, Notion, HubSpot | Connect for the organization again. The dialog shows Who can read it for the new account, with Cancel and Connect. |
| Granola, Mintlify, Documentation.AI | Connect for the organization again. Each Granola key and each docs address is its own connection. |
| tl;dv | Each person can connect one key of their own under Your accounts, while an admin allows it. Admins add organization keys with Connect for the organization, under Organization accounts. See Connect tl;dv. |
| HappyScribe, Holded, ClickUp, Asana, Linear, Factorial, Sesame, Zernio, monday.com, Attio | One connection only. Once connected, Connect for the organization is off with the hint "(App) supports one organization connection. Reconnect the existing account to change it." |
Open the app's page from Catalog or Sources to find the button. Each account gets its own source. Organization accounts lists the accounts, each with its own status. Click an account's name to open its own settings: Knowledge access, Content, History and Danger zone then apply to that account. On Sources the accounts share one row: see One row per app.
Rename a connection
Admins rename organization connections. The owner of a personal connection, such as a tl;dv key, renames it. Give a connection a name that tells it apart, for example one per team's key. It works for every app that has a connection. A webhook source and Local Uploads have no connection, so they have no Rename.
Open the connection
Open the source's page from Sources. In Organization accounts (or Your accounts, for your own personal connection), find the connection's row. A new connection is named after the person who added it, such as "tl;dv - " and their name.
Choose Rename
Click the three dots on the row ("More actions for" the connection's name) and choose Rename. The name becomes a field labelled "Connection name".
Save it
Type the new name and press Enter, or click outside the field. Press Escape to cancel.
The name has 1 to 120 characters, and extra spaces are collapsed. Gurusup keeps it: the app's own account name does not replace it later, and reconnecting does not reset it. The source takes the new name too and keeps its identity, what it learned and who can read it. Rename shows while the connection is connected, delayed, needs a reconnect or has an error, not while it is pending or after it is disconnected.
| Message | What to do |
|---|---|
| "Use a name between 1 and 120 characters." | Shorten the name, or type at least one character. |
| "Another connection already uses this name." | Pick another name. Upper and lower case do not make a name different. |
| "This connection no longer exists." | Someone disconnected it. Refresh Sources. |
Where to manage connectors
Open Sources in the sidebar. Company sources has one row per app or source, with its status and how much it has given Brain. The buttons at the top are Upload files, Import wiki and Connect source, and Add webhook source sits next to the search in Catalog; members get the first two and Connect source only opens Catalog. Import wiki moves a whole wiki over once: see Import a whole wiki.
Catalog lists every app as a row, grouped by category. Type in Search sources, or click View all on a category to see all its apps and All categories to go back. If nothing matches, Gurusup says "No sources match your search. Try another name or category." The button on a row reads Connect, View for people who cannot connect, or a Connected mark once the app is connected. Clicking any of them opens the app's page, where admins connect, reconnect and add accounts.
Click a row to open the source's page. It shows the sections that apply out of About, Knowledge access, Organization accounts, Content, History and Danger zone. Each section is explained in Check source status.
An app with several sources shares one row: see One row per app. Slack makes one source per channel and groups them in one row per Slack workspace: see One row per Slack workspace. A connection with no source yet has no row: open the app from Catalog.
Remove, disconnect and what stays
| Action | Shows for | What it does | What it keeps |
|---|---|---|---|
| Disconnect | A source that has a connection | Removes the whole connected account, all its sources included. Gurusup stops reading and deletes the credentials it stored for your organization. For Slack, questions Gurusup was still waiting on through that workspace are closed. | What Gurusup already learned, and the app's authorization in the other app |
| Remove source | A source with no connection, such as a custom webhook | Takes the source off Sources. A webhook's URL stops working. | What Gurusup already learned |
Disconnect opens a dialog "Disconnect [name]?" that says "Gurusup stops reading from [app]. What it already learned stays." Click Disconnect or Cancel. Remove source asks for a second click: the button turns red and reads Confirm.
Disconnect does not remove Gurusup from the other app. Gurusup deletes its own credentials and the webhooks it created there, but for Slack, Notion, HubSpot and Linear the approval you gave stays in place until someone uninstalls the Gurusup app in that app. Because other organizations can use the same account, uninstalling it there cuts them off too, so check first.
Disconnect and Remove source also cancel what that source had queued and Gurusup had not started on. Those items are not learned and cost no usage, what Gurusup already learned stays, and work already started carries on. A usage top-up or renewal only resumes content from sources that are still connected. See Follow ingestion.
Neither action deletes knowledge, and the app has no other way to delete what Gurusup learned from a source. If you need knowledge removed, contact support.
For what the source looks like afterwards, see Check source status.
When ingestion is paused or Demo Mode is on
A banner on Sources says "External ingestion is paused." or "Demo Mode is active." and adds that existing sources remain available but new external data cannot be added. Meanwhile:
| Where | What is off |
|---|---|
| Top of Sources | Upload files, Import wiki and, in Catalog, Add webhook source |
| Catalog | Nothing on the rows: their buttons still open the app's page. Connect for the organization on each page is off. |
| Every source page | Connect for the organization, Reconnect, Add data, Regenerate webhook token, the Notion export buttons, the Notion page picker, Import selected and changes to what a source brings in. Import history is hidden. Refresh status still works. In Demo Mode, Remove source and Disconnect are off too. |
| Stopping and removing, while ingestion is paused | Still work: Disconnect, Remove source, Cancel import on a Notion export and Remove on an uploaded file. |
| Incoming data | Ignored: Slack messages, Notion and HubSpot changes, webhook requests. A webhook request gets a 202 answer with "status": "ignored" and nothing is stored. |
When ingestion is paused, a click on something that is off returns "Ingestion is paused for this organization. Ask your organization admin to resume ingestion before adding content." In Demo Mode it returns "Demo Mode prevents changing external sources. Ask your organization admin to turn off Demo Mode to continue." Nothing on the page turns this off. Use Contact us on the banner at the top of the app and ask about your organization.