How to Consolidate HubSpot Calls and Texts in One Activity Feed Using Make

Learn how to route phone calls and text messages to the HubSpot company activity feed using Make automation, so all communication appears in one place.

Automation Basics

Jun 12, 2026

How to Consolidate HubSpot Calls and Texts in One Activity Feed Using Make

TABLE OF CONTENTS

Why This Problem Happens

The Solution: Routing Logic in Make

Step 1: Set Up Your Trigger

Step 2: Match Contact to Company

Step 3: Create Company-Level Activity

Step 4: Handle Edge Cases

Example Make Module Configuration

Testing Your Setup

Beyond Text Messages

Common Mistakes to Avoid

Next Steps

Get Help Building This

When you integrate call and text systems with HubSpot, a common frustration emerges: calls log to the company level, but texts scatter across individual contact records. This creates visibility gaps that slow down teams and fragment customer communication history.

This guide shows you how to fix this using Make automation to route all activities to the company feed.

Why This Problem Happens

By default, HubSpot integrations like Quo handle calls and texts differently:

Phone calls: Automatically associate with the company record if the contact belongs to that company

Text messages: Log only to the individual contact record

This means your team has to click through multiple contact profiles to see the full conversation history, instead of viewing everything in one consolidated timeline.

The Solution: Routing Logic in Make

The fix involves building a Make scenario that intercepts text message activities and explicitly associates them with the company record, not just the contact.

Step 1: Set Up Your Trigger

Create a Make scenario that watches for new SMS activities in your texting platform. For Quo or similar systems, this typically means:

Watch for new incoming texts

Watch for new outgoing texts

Capture the sender/recipient phone number and message content

Step 2: Match Contact to Company

Use HubSpot's API to:

Search for the contact by phone number

Retrieve the associated company relationships

Get the primary company ID

If the contact isn't yet linked to a company, you can implement partial match logic to auto-link based on company name patterns in your CRM.

Step 3: Create Company-Level Activity

Instead of creating the note or engagement on the contact only, use the HubSpot Create Engagement module in Make to:

Set the engagement type as "Note" or "SMS"

Associate it with both the contact ID and the company ID

Include the message content, timestamp, and direction

Key detail: Make sure you're passing the company association explicitly in the API call. Without this, HubSpot defaults to contact-only.

Step 4: Handle Edge Cases

Build in logic for:

Contacts without companies: Create a fallback that logs to contact only, or triggers a review task

Multiple company associations: Choose the primary company or most recently active

Unknown numbers: Create new contacts with proper company linking

Example Make Module Configuration


HubSpot > Create Engagement

Engagement Type: Note
Associations:
  - Type: Contact, ID: contact.id
  - Type: Company, ID: company.id
Body: SMS from phone: message.content
Timestamp: message.timestamp

Testing Your Setup

Send a test text to a contact with a known company association

Navigate to the company record in HubSpot

Check the activity feed—your text should appear alongside call logs

Verify the text also appears on the contact record

You want both associations, not just company-only.

Beyond Text Messages

This same routing pattern works for:

Email threads

Live chat transcripts

Support ticket updates

Meeting notes

Any activity that needs company-level visibility can follow the same association logic.

Common Mistakes to Avoid

Mistake 1: Only associating with the company, not the contact. This removes visibility at the individual level.

Mistake 2: Not handling contacts who work for multiple companies. Always define which company gets the activity.

Mistake 3: Forgetting to test with contacts added after the automation goes live. Partial match logic ensures new entries get properly linked.

Next Steps

Once your basic routing works, consider:

Adding sentiment analysis to SMS content

Auto-tagging activities by topic or urgency

Creating alerts when VIP companies receive texts

Building reports on response times by channel

Get Help Building This

Routing HubSpot calls and texts to a single company activity feed usually breaks at the company association step — either the contact isn't linked to a company yet, or the Make module isn't passing both IDs. If you've hit that wall, book a ZoomFlow session — one of our consultants can debug the scenario with you live and ship the working version in the same call.

Notion for eCommerce operations: build a product, supplier, and costing dashboard Zapier Team Plan Pricing: Tasks, Logins, and Cost for Real Estate Teams