Project tools tell the graph what is being worked on. Code tools tell it what shipped. Connect both and the Brain can answer "who asked for this, when was it decided, and did it ship?" with one chain of sources.
Code: GitHub
Fivo connects to GitHub and reads pull requests and the conversation on them: descriptions, comments and reviews. It does not analyse your source code. The goal is to link shipped work to the request, decision or incident that motivated it.
When you connect GitHub you choose the repositories that feed the graph. Each pull request thread becomes one episode, so a long review discussion turns into a few facts: what changed, who reviewed it, what was decided, when it merged.
Two things to know:
- Renaming a repository makes it a new source in Fivo. The old name stops being read and the new one is read from the start.
- An organization with OAuth restrictions can block Fivo from reading some repositories. They appear as sources Fivo cannot access.
GitHub cannot tell Fivo who can read a repository, so with organization scope its material is visible to the owner and to the people who took part in each pull request.
Project and task tools
Fivo connects to Jira, Linear, ClickUp, Asana, monday.com and Trello. For each you pick the projects, boards or spaces to read. Fivo reads tasks and their comments, so the graph knows what each ticket is about, who owns it, its status and how it changed over time.
Slack and Jira can report who has access to a project, and that membership governs who sees its facts in the graph.
Two directions: reading and sharing
These tools work in both directions.
Reading feeds the graph, as described above.
Sharing sends work out of Fivo. After a meeting, the tasks Fivo detected can be shared to Trello, Jira and other task tools from the report. When the card or issue moves in the external tool, the status syncs back to the task in Fivo and to the graph. See Tasks and commitments.
What the graph can do with it
- From request to shipped feature: a support ticket in Zendesk, a Linear issue and a GitHub pull request become one linked story. "Who asked for SSO and when?" gets an answer with three sources.
- Duplicated work: two teams building the same thing in two repositories is the kind of pattern the daily consultant audit surfaces.
- Decisions without follow-up: a decision recorded in a meeting with no ticket behind it shows up as an open loop.
- Status in plain language: "What is blocking the Atlas rollout?" answers with the ticket, who it is waiting on and the standup where it was discussed.
Limits
A Fivo task shared to Jira currently appears as two linked items in the graph rather than one. Very large workspaces (thousands of ClickUp spaces, for example) can take several passes to list completely; the AI Brain view shows progress while that happens.
Next
Connect the tools where your customers speak: Connect CRM and support tools.
Step-by-step guides
Each integration has its own guide with permissions, steps and troubleshooting.
Code:
Project and task tools:
- Connect Jira
- Connect Linear
- Connect ClickUp
- Connect Asana
- Connect monday.com
- Connect Trello
- Connect Microsoft To Do
Workflow:
- integrations
- github
- jira
- linear
- tasks