Mirror key LinkedIn events into HubSpot's Last Activity Date so reps can sort and prioritize leads natively — invites, replies, and messages synced by Hublead.
Overview
Make HubSpot’s default Last activity date reflect key LinkedIn milestones captured by Hublead, so your team can prioritize leads using HubSpot’s native sorting and views.
The key idea
HubSpot Last activity date updates when an activity is logged on the record (note, logged message, call, meeting, etc.).
So if a Hublead event only updates a timestamp property (and does not create an activity), HubSpot won’t move Last activity date.
What is already covered automatically
Hublead syncs your LinkedIn messages into HubSpot as logged activities, then it will automativacally updat ethe last acivity date
What typically needs a workflow
A common gap is Invitation Accepted:
- Last LinkedIn Invitation Accepted is usually a timestamp property update
- It may not create a HubSpot activityResult: Last activity date does not move unless you create an activity (example: a Note)
Prerequisites
- Hublead active
- Hublead properties enabled in HubSpot, at least:
- Last LinkedIn Invitation Accepted
- Last LinkedIn Message Sent (only for reference)
- Last LinkedIn Message Received (only for reference)
- Access to HubSpot Workflows
- Permission to create Notes via workflows
Free Guide
Get the HubSpot Outbound Handbook
Run an effective outbound campaign that keeps your pipeline full.
Step-by-step guide
Step 1: Confirm your Hublead timestamps are updating
Open a test contact and verify the LinkedIn timestamp properties are present and populated after real actions.
Step 2: Decide what you want to mirror into Last activity date
Recommended:
- Mirror Invitation Accepted only
Optional:
- Only add message-related mirroring if your Hublead setup does NOT log LinkedIn messages as activities in HubSpot.If messages are already logged, they already update Last activity date automatically.
Step 3: Create a guardrail property (recommended)
Create a contact property to prevent duplicate notes and avoid bumping activity from older timestamps:
- Name: LinkedIn activity mirrored to HubSpot
- Type: Date picker (or DateTime if available)
- Purpose: store the last LinkedIn timestamp you already mirrored
Step 4: Create the workflow (contact-based)
Path:Automation > Workflows > Create workflow > From scratch > Contact-based
Workflow name suggestion:Mirror LinkedIn invitation accepted into Last activity date
Enrollment trigger:
- Last LinkedIn Invitation Accepted is known AND has been updated
Re-enrollment:
- Enable re-enrollment on Last LinkedIn Invitation Accepted
Important:Do not add these triggers by default:
- Last LinkedIn Message Sent has been updated
- Last LinkedIn Message Received has been updatedThey are usually unnecessary because message sync is already a logged activity that updates Last activity date.
Step 5: Add a guardrail (avoid bumping with old data)
Add an If/then branch that continues only if the invitation accepted timestamp is newer than what you already mirrored.
Preferred logic:
- If Last LinkedIn Invitation Accepted is after LinkedIn activity mirrored to HubSpot
Alternative (if your portal supports it):
- If Last LinkedIn Invitation Accepted is after Last activity date
Step 6: Create a Note (this updates Last activity date)
Action: Create note
Suggested note template:Title: [Hublead] LinkedIn invite accepted
Body:Accepted at: {{Last LinkedIn Invitation Accepted}}Next step: send message #1 or enroll in your welcome sequence.
Step 7: Update the “mirrored” property
Action: Set property value
- LinkedIn activity mirrored to HubSpot = Last LinkedIn Invitation Accepted
Step 8: Test
- Have a test contact accept your LinkedIn invitation
- Confirm a note appears on the contact timeline
- Confirm HubSpot Last activity date moved forward
Best practices
- Mirror only the events that do not already create HubSpot activities (Invitation Accepted is the main one)
- Keep note titles consistent with a prefix like [Hublead]
- Always use a guardrail (comparison to “mirrored” date or Last activity date) to avoid bumps from historical backfills
- If you later mirror multiple LinkedIn events, use one branch per event or separate workflows to keep it readable
Free Guide
Get the HubSpot Outbound Handbook
Run an effective outbound campaign that keeps your pipeline full.
FAQs
Why does LinkedIn invitation acceptance not update Last activity date by default?
Because it updates a timestamp property, not a HubSpot activity. Only logged activities move Last activity date.
Do LinkedIn messages already update Last activity date?
Yes, if Hublead logs LinkedIn messages as activities in HubSpot. In that case, no workflow is needed for messages.
Is Hublead required for this setup?
Yes. Hublead provides the LinkedIn timestamp properties used by the workflow.
Which HubSpot plan do I need?
You need access to HubSpot Workflows and permission to create notes via workflows.
Can this create duplicate notes?
It can if no guardrail is used. A comparison property or date check prevents duplicates.
Can I mirror other LinkedIn events as well?
Yes, but it is recommended to only mirror events that do not already create HubSpot activities.
