The connector map: where your meetings actually land
A meeting produces five different kinds of output, and each belongs in a different tool. Here's how we think about routing — and an honest look at what's live versus what's next.
Ask what a meeting produces and you'll get "notes." Watch what a team does with a meeting and you'll see five different outputs going five different places.
The five outputs
- Work
- Tickets, cards, tasks — Jira, Trello, Asana, Monday, GitLab, GitHub.
- Signal
- Who needs to know, right now — Slack, WhatsApp.
- Record
- The decision, written down where it's findable — Docs, Confluence, Notion.
- Numbers
- Anything that belongs in a tracker — Sheets.
- Relationship
- What the customer actually said — HubSpot, Salesforce.
Most integrations products treat this as configuration: here are 40 connectors, wire up your own automations. We think routing is the product. Squirrel's job is to know that "we need to fix the onboarding drop-off" is a ticket, "the customer is worried about SSO" is a CRM note, and "we're going with Plan B" is a record — without you writing a rule for it.
What's live today
We're being deliberately unglamorous about this. A connector counts as live when it holds up on real meetings, not when the OAuth flow completes.
Live
- Slack
- Summaries, decisions and action items posted to the channel that owns the work.
- Jira
- Issues created in the right project, with owner and description carried over.
- Post-meeting recaps and nudges where a lot of teams actually live.
Next up
- Work
- Trello, Asana, Monday.com, GitHub, GitLab.
- Record
- Google Docs, Confluence.
- Numbers
- Google Sheets.
- Relationship
- HubSpot, Salesforce.
Scopes, not keys
Every connector is authorized separately, with the narrowest scope that lets it do its job. Squirrel asks for permission to create and comment — not to delete, not to administer, not to read your entire workspace history because it was convenient.
Connector requests are a roadmap input
The order we build these in is driven by what teams actually ask for. If the tool your work lives in isn't here, tell us — it's the single most useful thing you can send us right now.
The short version
- Routing is a product decision, not a settings page.
- Slack, Jira and WhatsApp are wired up today; the rest are queued.
- Narrow OAuth scopes per connector — an agent should be able to do exactly what you hired it for.
Give your company a second brain.
Squirrel captures every meeting, remembers every decision, and files the follow-up work for you.