Skip to content
  • There are no suggestions because the search field is empty.

HubSpot activities: tracking CRM interactions and follow-up

Understand how HubSpot records emails, calls, meetings, tasks and notes, and how to manage activity logging, visibility and follow-up.

Activities in HubSpot record the interactions and actions connected with CRM records such as contacts, companies, deals and tickets.

They help teams understand previous communication, coordinate follow-up and report on customer-facing activity. Some activities can be recorded automatically through connected tools, while others can be created or logged manually.

What HubSpot treats as an activity

HubSpot activities include:

  • Calls
  • Emails
  • Meetings
  • Notes
  • Tasks
  • LinkedIn, WhatsApp and SMS messages
  • Postal mail

These activities can be associated with one or more CRM records and displayed on the relevant record timelines.

Other events, including form submissions, marketing email engagement and website activity, may also appear on CRM timelines. However, these are engagement events rather than activities that users normally create or log manually.

Viewing activities on CRM records

The Activities tab on a CRM record provides a chronological view of recorded interactions.

Users can filter the timeline by activity type, date, assigned user and other available criteria. This makes it easier to locate a particular email, call, meeting, task or note without reviewing the complete record history.

HubSpot also provides activity index pages for viewing and managing activities across multiple records.

The activities and historical information available may depend on your HubSpot subscription. For example, activity visibility on record timelines is limited for some accounts using HubSpot’s free tools.

Creating and logging activities

Users can create new activities directly from a CRM record. Depending on the activity, this can include:

  • Sending an email
  • Making or logging a call
  • Scheduling or logging a meeting
  • Creating a task
  • Adding a note
  • Recording a message sent through another channel

When logging an activity, users should check that it is associated with the appropriate contact, company, deal, ticket or other relevant record.

Call and meeting outcomes, types and other details can also support reporting where they are configured and used consistently. The availability of custom activity options depends on your HubSpot subscription.

Email activities

Connecting an individual work inbox allows users to send one-to-one emails through HubSpot and use its email logging and tracking features.

Logging and tracking serve different purposes:

  • Logging stores the email on associated CRM records so authorised users can view the communication.
  • Tracking can notify the sender when a recipient opens an email or clicks a tracked link, subject to technical and privacy limitations.

Email logging is controlled by the user’s settings, the method used to send the email and the account’s email logging rules. Connecting an inbox does not mean that every message will automatically appear against every CRM record.

Teams should agree which emails should be logged and review any addresses or domains excluded from logging.

Calendar and meeting activities

Connecting a supported calendar allows HubSpot to check availability for scheduling pages and synchronise supported meeting information.

A connected calendar can help users:

  • Display availability through HubSpot scheduling pages
  • Prevent bookings over existing calendar events
  • Add supported HubSpot meetings to their calendar
  • Associate relevant events with CRM contacts

Calendar behaviour differs between Google Calendar, Microsoft 365 and Exchange. For example, Exchange does not support the same bidirectional synchronisation as Google Calendar or Microsoft 365.

Meetings that take place outside the supported synchronisation process can be logged manually against the relevant CRM records.

Calls, tasks and notes

Calls can be made through HubSpot where calling is available or logged manually when they take place elsewhere. Call outcomes, direction, type and notes can provide useful context for reporting and follow-up.

Tasks represent work that needs to be completed, such as calling a prospect or following up after a meeting. A follow-up task can also be created while logging certain activities.

Notes allow users to add internal context that does not belong in another activity type. Notes should be factual, relevant and suitable for everyone authorised to view the record.

Associations and data quality

An activity only provides useful context when it is associated with the correct records.

For example, a sales meeting may need to be associated with:

  • The attending contact
  • The contact’s company
  • The relevant deal

Users should review these associations when creating or logging activities. Missing or incorrect associations can leave teams with an incomplete history and reduce the reliability of activity reporting.

Teams should also avoid unnecessarily duplicating activities. This can happen when an integration logs an interaction automatically and a user records the same activity manually.

Testing activity tracking

Before rolling activity tracking out across your organisation, test the intended setup with a small number of users.

Testing should confirm that:

  • Emails are logged against the expected records
  • Email tracking behaves as intended
  • Calendar availability and meeting synchronisation work correctly
  • Activities have the correct record associations
  • Users can see only the information appropriate to their permissions
  • Follow-up tasks and notifications work as expected
  • Reporting includes the required activity information

This provides an opportunity to resolve configuration, permissions and privacy issues before more users connect their accounts.

Visibility, privacy and governance

Activities may contain correspondence, call information, meeting details and internal notes. Depending on permissions, this information may be visible to other users with access to the associated CRM records.

Your organisation should define:

  • Which interactions must be logged
  • Which activities are optional
  • What information should not be stored in activity notes
  • Who should be able to view, edit or delete activities
  • How email tracking and call recording should be used
  • How long activity information should be retained

Email tracking, call recording and communications monitoring should be reviewed against your organisation’s privacy, employment and data protection obligations.

HubSpot provides the technical controls, but your organisation is responsible for deciding how activity information should be recorded, accessed and governed.

What can Forbidden help with?

Forbidden can help you:

  • Configure inbox and calendar connections
  • Define consistent activity-logging practices
  • Review record associations and activity visibility
  • Configure call and meeting outcomes or types where available
  • Test activity capture before wider rollout
  • Build reports using activity data
  • Review permissions and identify potential governance considerations

Your organisation remains responsible for approving its monitoring, privacy, retention and data-handling policies.

Further information