Changelog: Sources

What we've shipped in Gurusup Brain, newest first.

  1. Sources

    Each source's panel has tabs and connects without leaving it

    Before you connect a tool, you want to know what Gurusup Brain will read from it and what you will be able to ask afterwards. That used to be scattered, and connecting meant a dialog on top of the source's panel.

    Now each source's panel is organized in tabs, and you connect or reconnect inside it. About explains what Brain reads, gives example questions and says how the source stays current. Connect, which becomes Connections once the source is connected, holds the form and the steps to create a token. Actions appears when the source has something to do. A tab only shows when there is something to put in it.

    • Under Connections, Current connection shows which account is connected and what Brain reads from it.
    • The status sits next to the name: Connected, Needs reconnect or Error.

    The result is that an admin can decide whether a source is worth connecting, connect it and check that it works, all from one place.

  2. Sources

    Connect ClickUp, Asana, Linear, monday.com and five more tools

    A lot of what a team knows lives in its project tracker, its CRM, its invoicing tool, its meeting notes and its public docs. When Gurusup Brain could not read those tools, that knowledge stayed out of every answer, and someone had to go and look it up by hand.

    Sources now offers nine more tools, and an admin connects each one by pasting a token or an address. Brain starts reading as soon as you connect, so the first content shows up in Ingest sooner instead of waiting for the next pass.

    • Projects and tasks: ClickUp (tasks in shared spaces, with subtasks, checklists, fields and comments), Asana (shared projects, status updates and tasks with comments), Linear (public issues, projects, documents, cycles, releases, customers and initiatives) and monday.com (public boards, with items, subitems and comments).
    • Customers and finance: Attio (companies and deals, with their notes, tasks, comments and call transcripts) and Holded (invoices, estimates, orders and purchases, each with its lines and contact). When you paste the Holded token, the panel lists the permissions Brain needs and marks the ones it lacks.
    • Meetings: Granola, with the notes, summary and transcript of each meeting your team shares.
    • Public docs: Mintlify and Documentation.AI. Paste the address of your published docs, no key needed, and Brain keeps them current on its own.

    With these connected, your agent can answer questions that cross tools, such as "which open deals in Attio are waiting on an issue that is still open in Linear?"

  3. Sources

    Bring your current wiki into Gurusup Brain in one upload

    Many teams already have years of knowledge in a wiki or a notes tool. Moving it meant knowing which export to make, and many export formats could not be read, so whole wikis stayed behind.

    Now setup starts by asking Where does your team's knowledge live?, with two paths: Connect live sources and Migrate your current wiki. In Sources, Import from another wiki sits next to Upload files. Pick your tool and the dialog gives you the export steps with that tool's own menu names, then you drop the file. Each page or note comes in as its own document, so you can upload a whole wiki at once.

    • Guided tools: Confluence, Obsidian, Logseq, Evernote, Notion, BookStack, MediaWiki, Roam Research, TiddlyWiki, GitBook, Outline, Joplin and a Markdown folder. Other gives general steps for anything else.
    • Upload files also reads HTML pages, .org, AsciiDoc, Obsidian Canvas, TiddlyWiki and TextPack files, plus exports from BookStack, MediaWiki, Evernote, Roam and TiddlyWiki.
    • Tool folders such as .obsidian or .trash are skipped, and links between notes keep working, also in ZIP files made on macOS with accented names.

    Once it is in, your old wiki answers next to your live tools: your agent can tell you what the onboarding guide in Confluence says and whether last week's Slack thread changed it.

  4. Sources

    Sources groups your Slack channels by workspace

    If you connected many Slack channels, Sources showed each one as its own card and its own slice of the Contribution to the Brain chart. With dozens of channels the page was long, and it was hard to see what Slack as a whole was bringing in.

    Now you get one card and one slice per Slack workspace, named Slack · followed by the workspace name, with its channels, documents and status added up. Click Manage on the card to see every channel, each with its documents, memories, contribution and status.

    • You manage the workspace connection, not each channel, so channel rows no longer have their own Manage button.
    • In the chart, channels that are no longer connected share one Slack slice instead of one slice each.

    At a glance you can compare how much Slack contributes against Notion, HubSpot or your uploaded files, and spot a quiet channel without scrolling through a list of cards.

  5. Sources

    Meetings from HappyScribe come into Gurusup Brain on their own

    Decisions are made in meetings, and recordings tend to stay in the tool that made them. If your team records with HappyScribe, what was agreed in those meetings never reached your company memory unless someone copied it over.

    Now an admin can connect HappyScribe from its panel in Sources. Copy the API key of an account that owns or administers your HappyScribe workspace (Settings > Personal > API), paste it in the Connect tab and click Connect. Each meeting HappyScribe finishes after that comes in as one document, with its summary, action items and transcript.

    • Only meetings that finish after you connect come in.
    • HappyScribe does not label private meetings yet, so every meeting comes in for your whole organization. The panel shows this before you connect.
    • If HappyScribe stops accepting the key, the status shows Needs reconnect and Connections tells you to paste a new one. Your access and settings stay as they were.

    Your agent can now answer what was decided in a call and connect it with the rest of your work, for example whether the action items from Tuesday's meeting already have an owner in your project tracker.

  6. Sources

    Choose which Notion pages and HubSpot deals go into Gurusup Brain

    Not everything in a Notion workspace or a CRM belongs in your company memory. HubSpot used to offer only a Backfill button that brought in everything it could reach, with no say in what came in.

    Now Choose content lets you pick. Search, filter deals by pipeline, stage and date, tick what you want and press Import selected. In Notion, Choose content replaces Backfill.

    You can start with the pipeline or the pages that matter, for example this quarter's open deals and the sales playbook, and add more later. A focused memory gives more precise answers, and you stay in control of what goes into it. If you change your mind, open Choose content again and import more.

  7. Sources

    Webhooks tell you when content has arrived

    A webhook lets any tool send content to Gurusup Brain, even one we do not connect to yet. But after creating one there was no way to know whether anything had arrived, so you could not tell a working setup from a broken one.

    Now each webhook shows Waiting for content until the first delivery and Content received after it.

    • Generate new URL replaces a URL you can no longer see.
    • Admins can paste up to 1 MB of JSON with Send JSON, to try the webhook or send content without setting anything up outside.

    You can wire up an internal tool or an automation, send one test event and see straight away that it reached your memory, before you rely on it. If the status stays on Waiting for content, the problem is on the sending side.

  8. Sources

    Sources shows what is really connected

    A round of fixes so Sources reflects what you have connected and what each source contributes.

    Fixes

    • Each source's share of your memory is now right. Slack and Notion used to show 0%.
    • An app whose authorization you left halfway no longer shows as connected.
    • Opening a HubSpot source with a single connection no longer leaves a blank screen.
    • Local uploads no longer offer a Remove source button that always failed.
    • Get started shows loading rows, and a Try again button if your apps fail to load.
    • ZIP and TAR.GZ files made on a Mac no longer process or charge for the metadata files macOS adds.
  9. Sources

    Upload several files at once, including Word, PowerPoint and Excel

    File uploads used to take one PDF at a time. Now you can pick or drag several files together, follow each one's progress, and upload .docx, .pptx and .xlsx as well as PDF. If one file fails, the rest keep going and you can retry it.

    Encrypted or image-only PDFs still can't be read.