Connect your tools | Docs | Fivo University

Your graph is only as good as what feeds it. Fivo connects to the tools your team already uses and reads their history, so the Brain knows your work from day one and keeps learning as new material arrives.

What you can connect

Fivo groups integrations into families. Each family has its own articles with details:

Email and calendar: Gmail, Outlook, Google Calendar and Microsoft calendar. See Connect email and calendar.
Chat and documents: Slack, Microsoft Teams, Discord, Telegram, Notion, Confluence, Google Drive and Google Docs. See Connect chat and documents.
Code and project tools: GitHub, Jira, Linear, ClickUp, Asana, monday.com and Trello. See Connect code and project tools.
CRM, support and billing: HubSpot, Pipedrive, Salesforce, Attio, Close, Zoho CRM, Intercom, Zendesk and Stripe. See Connect CRM and support tools.

Meetings are a source too, with their own reports rather than an integration. See Meeting reports.

Step-by-step guides

Every integration has its own guide with permissions, steps and troubleshooting, grouped by family:

Email and calendar

Chat and documents

Code and project tools

CRM, support and billing

How a connection works

Open Integrations in app.fivo.ai and pick a tool. Most tools sign in with OAuth: the provider asks you to approve Fivo, and no key is copied anywhere. A few take an API key that you create in the provider and paste into Fivo, where it is validated before it is saved.

Once connected, Fivo lists what it can read in that account (channels, boards, projects, repositories, mailbox) and starts reading. In the AI Brain view you can watch each source move from "Waiting" to "Reading" to "Done", and see how many items were read.

Personal or organization

Every connection has a scope, and the scope decides who sees what it brings into the graph.

Personal: what this source brings is visible only to you. Not even the organization owner can see it. Email is always personal.
Organization: what this source brings is visible to the people who can also see it in the original tool. A Slack channel is visible to its members, a Jira project to the people with access to it.

You choose the scope when you connect a source. Only the organization owner can bring a source in with organization scope. The scope cannot be changed afterwards without reconnecting, because changing it would publish to the company material that somebody brought in privately.

What to connect first

Connect your calendar first so your meetings reach Fivo as reports (see Meeting reports). Then add the one tool where most of your written work happens: Slack for most teams, HubSpot or another CRM for sales, Jira or Linear for product. One or two good sources answer more questions than ten half-used ones.

When a source cannot be read

Some accounts do not let Fivo read their history. A personal Microsoft account, for example, does not give access to Teams chats; you need a work or school account. If a tool you connected earlier only had permission to share reports, Fivo will ask you to reconnect it to add reading. Sharing keeps working meanwhile.

Fivo also marks sources it cannot access, such as a private Slack channel the bot was not invited to, so you know what the graph is missing. The Brain status in the app lists these blind spots.

Keeping sources fresh

Connected sources are synced on a regular cadence, and tools with webhooks send changes as they happen. The AI Brain view shows the last sync of each source. If a connection expires or loses permissions, Fivo flags it as needing attention instead of failing silently.

integrations
setup