How do I connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly?
AI Agent Automation Platforms

How do I connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly?

11 min read

Connecting AiSDR to HubSpot the right way ensures every email, LinkedIn touch, and meeting logged by AiSDR appears on the correct contact record in HubSpot. This makes it much easier to track pipeline, enforce SLAs, and attribute revenue to outreach done in AiSDR.

Below is a step‑by‑step guide to help you set up the integration, configure activity logging, and troubleshoot common sync issues so everything flows smoothly from AiSDR to HubSpot.


1. What the AiSDR–HubSpot integration actually does

When configured correctly, connecting AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly can:

  • Create or update HubSpot contacts from AiSDR leads
  • Log outbound and inbound emails as activities on the associated contact
  • Record LinkedIn touches (InMails, connection requests, profile visits, comments, etc.) as contact activities
  • Sync meetings scheduled through AiSDR sequences or booking links into your HubSpot meetings and timeline
  • Push engagement data (opens, clicks, replies, etc.) to HubSpot for reporting and workflows

Understanding these capabilities helps you set proper expectations before connecting AiSDR to HubSpot.


2. Prerequisites before you connect AiSDR to HubSpot

Before you start the integration, make sure you have:

  • HubSpot permissions
    • Super Admin or Admin-level permissions, or
    • Access to “App Marketplace” and “Integrations”
    • Access to create/edit contacts, activities, and meetings
  • AiSDR admin access
    • Ability to manage integrations for your AiSDR workspace
  • Email and calendar connected in AiSDR
    • Your outbound email address (Gmail, Outlook, or SMTP) connected to AiSDR
    • Your calendar connected (if you want meetings to sync back to HubSpot)

If any of these are missing, fix them first to avoid partial or broken sync when you connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly.


3. How to connect AiSDR to HubSpot (initial setup)

The exact UI can change as both products evolve, but the standard flow is similar to other sales tools.

Step 1: Open integrations in AiSDR

  1. Log in to your AiSDR account.
  2. Go to Settings (usually via your avatar or sidebar).
  3. Open the Integrations, Apps, or CRM tab.
  4. Look for HubSpot in the list of available integrations.

Step 2: Authorize HubSpot

  1. Click Connect, Install, or Authorize next to HubSpot.
  2. A HubSpot login window will open:
    • Log in to the correct HubSpot account.
    • If you manage multiple portals, choose the one you want to connect to AiSDR.
  3. Review the permissions AiSDR is requesting:
    • CRM Objects: contacts, companies, deals (read/write)
    • Engagements: emails, tasks, notes, calls, meetings (read/write)
    • Settings & scopes as required by AiSDR
  4. Click Authorize or Connect app.

You have now connected AiSDR to HubSpot at a basic level. Next, you need to configure how emails, LinkedIn touches, and meetings sync.


4. Mapping fields between AiSDR and HubSpot

Good field mapping is critical to ensure activities match the right contact when you connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly.

4.1 Core contact mapping

In AiSDR, navigate to the HubSpot integration settings and look for Field Mapping or Object Mapping. Ensure you map:

  • Email (primary)hubspot_contact.email
  • First namehubspot_contact.firstname
  • Last namehubspot_contact.lastname
  • Company namehubspot_contact.company or hubspot_company.name
  • Phonehubspot_contact.phone or mobilephone
  • Job titlehubspot_contact.jobtitle
  • LinkedIn URL → Custom contact property (e.g., linkedin_profile_url)

Make email the authoritative unique identifier for matching contacts. This prevents duplicate contacts when syncing activities.

4.2 Company and deal mapping (optional but recommended)

If AiSDR tracks account or opportunity data:

  • Map Account/Company Name to HubSpot Company.
  • Map Pipeline Stage, Deal Name, ARR/Value, etc. to HubSpot Deal properties (if AiSDR supports deal sync).

This allows sequences and activities in AiSDR to be connected to specific companies and deals in HubSpot.


5. Configuring email sync from AiSDR to HubSpot

To connect AiSDR to HubSpot so emails sync back correctly, you must configure both email account connection and engagement logging rules.

5.1 Ensure your email is connected in AiSDR

  1. In AiSDR, go to Email Settings or Channels.
  2. Connect your work email (Gmail, Outlook, or SMTP).
  3. Verify sending (SPF/DKIM, if prompted) to avoid deliverability issues.

AiSDR needs this account to send and track emails that will later be logged in HubSpot.

5.2 Choose how emails are logged in HubSpot

In the AiSDR–HubSpot integration settings, configure:

  • Log outbound emails to HubSpot

    • Enable “Sync outbound emails to HubSpot” or similar.
    • Choose Engagement Type: usually “Email”.
    • Decide whether to sync:
      • All emails
      • Only sequence emails
      • Only replies or only certain campaigns
  • Log inbound emails (replies)

    • Enable “Sync replies” so HubSpot sees responses as email engagements.
    • Check whether AiSDR will also update contact properties (e.g., “Last contacted”, “Last reply date”).

5.3 Match emails to existing HubSpot contacts

To connect AiSDR to HubSpot so emails sync back correctly and attach to the right contact:

  • Configure AiSDR to match by email address first.
  • If no contact exists, decide whether AiSDR should:
    • Create a new contact in HubSpot, or
    • Skip logging to avoid clutter.

Most teams enable automatic creation to ensure every outreach target exists in HubSpot.


6. Syncing LinkedIn touches from AiSDR to HubSpot

LinkedIn touches aren’t native emails, so you need to decide how they appear in HubSpot.

6.1 Types of LinkedIn activities AiSDR can track

Depending on your AiSDR plan and features, you may be able to log:

  • Connection requests
  • InMails
  • Direct messages
  • Profile visits
  • Comments or likes on posts
  • Sequence steps that involve LinkedIn tasks

Confirm in AiSDR which LinkedIn touch types are supported for HubSpot sync.

6.2 Configuring LinkedIn sync in AiSDR

In the HubSpot integration settings:

  1. Find Activity types, Engagement mapping, or Channel mapping.
  2. For LinkedIn, map to one of:
    • Task (e.g., activity type = “LinkedIn touch”)
    • Note with a special label (e.g., “LinkedIn action”)
    • Custom activity type if your HubSpot portal supports it

Configure:

  • Which LinkedIn events to log

    • Simple option: “Log all LinkedIn steps as activities.”
    • Advanced: Only log “connection requests” and “InMails,” not profile views.
  • Activity details

    • Include: message content, link to the profile, sequence name, and sender.
    • Add tags or a prefix in the subject line, e.g., [AiSDR LinkedIn] Connection request.

This makes it easy to filter LinkedIn touches in HubSpot reports.

6.3 Ensuring correct contact matching for LinkedIn

LinkedIn touches must be tied to a specific email and contact in AiSDR. To connect AiSDR to HubSpot so LinkedIn touches sync back correctly:

  • Make sure every LinkedIn prospect in AiSDR has:
    • An email address
    • A LinkedIn URL
  • Ensure the AiSDR contact is linked to the right HubSpot record via email or contact ID.
  • Avoid using generic or personal emails that might map to the wrong contact in HubSpot.

7. Syncing meetings and calls from AiSDR to HubSpot

If you’re using AiSDR to book meetings or log calls, you can sync those into HubSpot as meetings and calls activities.

7.1 Connecting your calendar in AiSDR

  1. Go to Calendar or Meetings in AiSDR.
  2. Connect your Google Calendar or Microsoft 365/Outlook.
  3. Configure your availability, meeting links, and time zones.

AiSDR uses your calendar connection to detect meetings created through its flows.

7.2 Mapping AiSDR meetings to HubSpot

In the AiSDR–HubSpot integration settings:

  • Enable meeting sync

    • Turn on “Sync meetings to HubSpot.”
    • Choose whether meetings will be created as:
      • Engagement: Meeting
      • With organizer and participants correctly set.
  • Field mapping for meetings

    • Title → Engagement subject (e.g., “Discovery Call – AiSDR”)
    • Date/time → Meeting start/end
    • Location → Zoom/Meet link or physical address
    • Description → Meeting notes or link back to AiSDR
  • Contact association

    • Meetings should be associated to:
      • The primary HubSpot contact(s)
      • Optionally: company and deal records

This is central to connecting AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly for your full account history.

7.3 Syncing calls and call outcomes (if supported)

If AiSDR has dialer features:

  • Enable call sync in the HubSpot integration.
  • Map:
    • Call activity → Engagement: Call
    • Call outcome → HubSpot call outcome property (e.g., “Connected”, “No answer”)
    • Recording URL → call engagement notes or properties.

8. Best practices to ensure everything syncs back correctly

To connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly at scale, follow these guidelines:

8.1 Standardize email domains and sender addresses

  • Use consistent work domains (e.g., @company.com), not personal addresses.
  • Avoid sending from multiple random aliases that don’t exist in HubSpot.

8.2 Keep AiSDR and HubSpot contact data aligned

  • Sync contacts from HubSpot into AiSDR where possible and attach sequences to those, rather than creating brand new records in AiSDR only.
  • Regularly deduplicate contacts in HubSpot (by email and name) to avoid mismatched logging.

8.3 Use naming conventions

Set clear naming conventions for:

  • Sequences in AiSDR (e.g., Outbound – US – SaaS – C-suite).
  • Meeting types (e.g., AiSDR – Intro, AiSDR – Demo).
  • Activity subjects (e.g., prefix with [AiSDR] for easy filtering in HubSpot).

This makes it easy to report on AiSDR activity inside HubSpot.

8.4 Test with a pilot group before full rollout

  1. Pick 1–2 reps and a few test contacts.
  2. Run sample emails, LinkedIn steps, and meeting bookings.
  3. Verify in HubSpot:
    • Are activities logged exactly once?
    • Are they tied to the correct contact/company/deal?
    • Are timestamps, owners, and notes accurate?

Fix any issues before you connect AiSDR to HubSpot for your entire team.


9. Common issues and how to troubleshoot them

Even when you connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly initially, problems can emerge over time. Here are frequent issues and fixes.

9.1 Emails not appearing in HubSpot

Possible causes:

  • HubSpot integration was disconnected.
  • Email account in AiSDR is not connected or re-auth is required.
  • Activity logging toggle for emails is off in AiSDR.
  • Email was sent from a non-connected address.

Fixes:

  1. Reconnect HubSpot in AiSDR and confirm scopes.
  2. Reconnect your email in AiSDR and send a test email.
  3. Verify in AiSDR’s integration settings that “Log outbound emails” is enabled.
  4. Confirm the recipient’s email matches a HubSpot contact and that contact creation is allowed if none exists.

9.2 LinkedIn touches missing in HubSpot

Possible causes:

  • LinkedIn activity sync is disabled.
  • Contact in AiSDR lacks a mapped email or LinkedIn URL.
  • AiSDR is logging LinkedIn touches as a type HubSpot is filtering out.

Fixes:

  1. Turn on LinkedIn activity sync and ensure correct mapping (e.g., Task or Note).
  2. Update the AiSDR contact with the correct email linked to a HubSpot contact.
  3. Adjust filters in HubSpot to include AiSDR-created tasks/notes.

9.3 Meetings not syncing or appearing on the wrong contact

Possible causes:

  • Calendar isn’t connected in AiSDR.
  • Meeting owner doesn’t match any HubSpot user.
  • Multiple contacts share the same email or the contact isn’t in HubSpot yet.

Fixes:

  1. Connect or re-auth your calendar in AiSDR.
  2. Map AiSDR users to HubSpot users in integration settings (if available).
  3. Deduplicate contacts in HubSpot and ensure AiSDR is using the primary email.

10. How to verify your integration is working

Once you connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly, you should regularly verify the integration.

10.1 Spot-check a contact

  1. Choose a prospect that:
    • Received AiSDR emails
    • Got a LinkedIn touch
    • Booked a meeting
  2. Open the contact in HubSpot and confirm:
    • Email engagements show as “Email” from the AiSDR sender.
    • LinkedIn touches appear as notes or tasks with clear descriptions.
    • Meetings are visible in the contact’s activity timeline with correct time and participants.

10.2 Build an activity-based report in HubSpot

Use HubSpot reports to confirm data volume and sources:

  • Filter by:
    • Activity type = Email, Meeting, Task/Note
    • Source/Integration = AiSDR (if tagged)
  • Group by owner, sequence, or campaign.

This quickly highlights if certain activity types are not syncing or if some reps are misconfigured.


11. When to contact support

If you’ve followed these steps to connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly and still see issues:

  • Export logs from AiSDR (if available) and take screenshots of:
    • AiSDR activity
    • Corresponding HubSpot contact timeline
  • Note:
    • Time of activity
    • Contact email
    • User who triggered it
  • Contact AiSDR support first (they control the integration behavior), and share:
    • Your HubSpot portal ID
    • Your AiSDR workspace
    • Specific contacts/activities that failed to sync

They can check API logs and adjust integration settings or fix bugs on their side.


By following these steps and best practices, you can connect AiSDR to HubSpot so emails/LinkedIn touches and meetings sync back correctly, giving your sales and RevOps teams a single source of truth inside HubSpot while still taking full advantage of AiSDR’s outbound automation.