Connect Close | Docs | Fivo University

Close is built around the lead and the activity logged against it. Connecting it gives the Brain each opportunity together with the calls, emails, notes and meetings on its lead, so your AI can answer about an account with the full record behind it.

What it adds to your Brain

Fivo reads your Close opportunities and the activities on their leads:

The opportunity: status, value and currency, won date, the lead (company) it belongs to and the lead's contacts and domain.
The activities logged on the lead: notes, calls, emails and meetings, with the user who logged them and the date.

In Close, activities belong to the lead rather than to a single opportunity, so Fivo threads a deal with its lead: everything logged on that lead sits next to its opportunities. Example question: "Which leads with an open opportunity had a call logged this week, and what was discussed?"

Before you start

You need a Close user who can see the leads and opportunities you want Fivo to read. Depending on your role settings, an admin may need to connect.
Close grants every connected app full access to the account; this is how Close works, not a choice Fivo made. When you approve Fivo, Close asks for full access and for permission to keep the connection alive without signing in again. Fivo reads opportunities and activities for the Brain, and writes a note or a task on a lead only when you share a meeting report or action items yourself.

Step by step

Open Integrations in the app and choose Close.
Click Connect. Close opens its authorization page.
Sign in to Close and approve the access.
Fivo confirms the connection, records your Close organization on its own and registers a webhook so changes arrive live.
Choose a Lead. This is the Close lead the notes and tasks will be added to when you share a meeting report or action items. The picker is required by the Close integration, but it does not limit what the Brain reads.

What happens next

Fivo reads your opportunities first, then the notes, calls, emails and meetings on their leads. In the AI Brain view the Close source moves from queued to reading to done.

After the first read, changes arrive live: Close sends the whole object when an opportunity or an activity is created or updated, so Fivo stores it without going back to ask. The regular sync pass still runs to catch anything the webhook missed.

Who can see what: with organization scope, Close material is readable by the people who are users in your Close organization, matched by email to members of your organization. Close permissions are role-based rather than per record, so this roster is a faithful picture of who could read it in Close. See Permissions: what your Brain can see.

Disconnect

Open Integrations, select Close and click Disconnect. Fivo removes the webhook it registered in Close, stops reading and deletes the stored credentials. What the Brain already learned stays in the graph; connecting the same organization again resumes reading. To take Close material out of the graph, use Remove from graph on the Close source in the AI Brain view.

Troubleshooting

"Reconnect to read". The connection was revoked in Close or has expired. Click Reconnect and approve again.
Nothing appears yet. The first pass walks opportunities and then each activity type. Check the source status in the AI Brain view.
Changes do not arrive live. Close limits how many webhook subscriptions an organization can have, and that limit is shared with every other app you connected. If Fivo's webhook could not be created, the regular pass still brings changes in; freeing a subscription in Close and reconnecting fixes it.
Only some activities show up. Fivo reads notes, calls, emails and meetings. Other activity types are not read.

integration
crm