The Planhat integration sends the AI summaries of conversations recorded by Four/Four to the matching company in Planhat, so customer success teams see them on the company timeline. Four/Four does not import companies, end users or deals from Planhat. It works alongside your main CRM and uses the IDs of your CRM accounts and contacts to find the matching Planhat records. The only data Four/Four reads from Planhat is your active users, which it refreshes about every five minutes to attribute conversations to the right Planhat user.
Connect Planhat
You need a CRM already connected to Four/Four (Salesforce, HubSpot, Dynamics 365 or Attio), and permission in Planhat to create a Private App and API access token. See the Planhat Help Center for how. The token must be able to read companies, end users and users and to create and edit conversations.
In Planhat, create a Private App and copy its API access token.
In Four/Four, go to Settings > Connections.
Under Customer relationship management, find Planhat and click Connect.
In the Connecting Planhat window, paste the token into API access token.
Choose the Planhat service: Production for your live account or Demo for a Planhat demo account.
Click Connect. If the token is accepted you see "Planhat has been connected." and the card shows Connected.
What Four/Four writes to Planhat
When a conversation recorded by Four/Four (for example by the Four/Four notetaker) finishes processing, Four/Four creates a Planhat Conversation if all of these are true:
The conversation has an AI summary.
The conversation is linked to an account in a connected CRM.
A company exists in Planhat whose Source ID matches that CRM account's ID. This is normally set when you sync your CRM into Planhat.
If any of these is missing, nothing is sent for that conversation. Conversations imported from other tools, such as Gong or Zoom, are not sent. This is on by default; to turn it off, ask your Four/Four team.
Each Planhat Conversation has the subject "conversation title (Four/Four)", the meeting date, the conversation type, and a description with a link to the conversation in Four/Four followed by the summary. Contacts linked to the conversation are attached as end users when a Planhat end user has a Source ID matching the CRM contact's ID. Planhat users are attached when they match the meeting organiser or a participant by email address. If the conversation changes in Four/Four, the Planhat Conversation is updated; if it is deleted in Four/Four, it is deleted from Planhat. Four/Four does not change companies, end users or any other Planhat data.
Troubleshooting
Authentication failed. The token has expired, been revoked or lacks the required access. Click Disconnect, create a new token and Connect again.
"Planhat could not be connected." Check the token and that you picked the right Planhat service. A Production token does not work with Demo, and the reverse.
Conversations are not appearing in Planhat. Check that the conversation has a summary, is linked to a CRM account, and that the Planhat company's Source ID matches that account's ID. Conversations recorded before you connected Planhat may not be sent until they are next updated.
To disconnect, click Disconnect on the Planhat card.
Permissions
Connecting and disconnecting Planhat in Four/Four needs the Manage connections permission. Without it, you cannot connect or disconnect the integration.