Connect your CRM, email, and calendar to Followups

Who this guide is for

This guide is for the person responsible for connecting Followups to the team’s sales stack—typically an operations owner, CRM administrator, or team lead with permission to authorize the relevant accounts. It is useful before a pilot because it shows which connection decisions belong to the account owner rather than to an individual rep.

Before you start

Confirm which Google account, HubSpot workspace, inbox, calendar, and communication channel belong to the pilot. You should have authorization to grant access for each selected system. The recording contains an earlier product name in parts of the interface; the notes here describe only the visible flow and do not ask you to bypass provider security warnings.

Connection steps

1. Open the Integrations area and choose the account that should provide the Google sign-in. Review the requested Gmail and calendar permissions against the workflow you agreed to configure.
2. Select HubSpot and authorize the intended workspace. Check the workspace name before continuing so customer, contact, deal, and activity updates do not target the wrong account.
3. Return to the Integrations list and confirm that the expected Google Calendar and Contacts connection is shown as connected before moving to communication channels.
4. Connect only the channel required by the pilot, such as WhatsApp or Telegram, using the account or phone number controlled by the team. Follow the provider-owned authorization screen rather than sharing credentials in chat.
5. Read the final connection states in the Integrations list. A connected label is the checkpoint; it is not proof that every workflow action has been configured or approved.

Expected result

The selected CRM, Google services, and communication channel appear in the Integrations list with their connection state. That gives the implementation a defined set of systems to read from or write to. The next step is to agree which sales event activates the workflow, which fields or drafts it may prepare, and which actions remain under human review.

Troubleshooting

If Google or another provider shows an unexpected verification, permission, workspace, or account warning, stop and confirm the current authorized sign-in path with the Followups team; do not bypass an unfamiliar security warning. If a connection returns to the list without a connected state, check whether the account has the required admin permission and whether pop-up or cross-site sign-in controls interrupted the provider flow.