Create a Salesforce follow-up task after a LinkedIn conversation with Hublead
A record-triggered Flow that gives the rep a follow-up Task in Salesforce each time a LinkedIn conversation is logged, one per person, never duplicated.
- WhenHublead logs a LinkedIn TaskMessage from the last 7 days
- ThenCheck for an open follow-upOne per person
- ThenCreate a Task for the repDue in 2 days
What you get
- A follow-up Task in Salesforce each time a LinkedIn conversation is logged
- One open follow-up per person, not one per message
- Next steps in the rep's Salesforce task list, where the rest of the pipeline already is
Prerequisites
- Hublead connected to Salesforce. A Salesforce admin installs Hublead in the org once, then each rep clicks Connect Salesforce in the extension
- Reps who sync their conversations: a conversation syncs when the rep opens it on LinkedIn, automatically if auto-sync is on, or with the Sync messages button
- A Salesforce admin, or a user who can create and activate Flows
Problem
A LinkedIn conversation ends with "let's talk next week", and the next step lives in the rep's head. Salesforce has the conversation, but no task, so the follow-up depends on memory. The busier the week, the more of them slip.
-
1. Open one Task logged by Hublead
Open a Lead or Contact whose LinkedIn conversation was synced and open one of its LinkedIn Tasks. Hublead logs synced messages as Tasks with the status Completed, dated in the Due Date. Copy the Subject and check that Assigned To is the rep who had the conversation: the Flow uses both. If it shows another user, set Assigned To ID in step 5 to
{!$Record.CreatedById}instead. -
2. Create a record-triggered Flow on Task
Go to Setup → Process Automation → Flows → New Flow and pick Record-Triggered Flow. Set:
- Object: Task
- Trigger the Flow When: A record is created
- Optimize the Flow for: Actions and Related Records
-
3. Keep only recent LinkedIn messages
Set Condition Requirements to Formula Evaluates to True and paste, with the Subject you copied in step 1:
AND(CONTAINS({!$Record.Subject}, "paste the Subject here"), NOT(ISBLANK({!$Record.WhoId})), {!$Record.ActivityDate} >= TODAY() - 7)The last part skips messages older than 7 days, so the first sync of a long conversation does not create follow-ups for last year's messages.
-
4. Skip people who already have a follow-up
Add a Get Records element on Task, with the conditions Name ID equals
{!$Record.WhoId}, Subject equalsFollow up on LinkedIn conversationand Closed equalsFalse, keeping only the first record. Then add a Decision with one outcome, No open follow-up: the record from Get Records Is NullTrue. -
5. Create the follow-up Task
On the No open follow-up path, add Create Records for one Task:
- Subject:
Follow up on LinkedIn conversation. It must not contain the Hublead Subject, or the Flow would trigger on its own Tasks - Assigned To ID:
{!$Record.OwnerId} - Name ID:
{!$Record.WhoId}and Related To ID:{!$Record.WhatId} - Due Date Only: a formula resource of data type Date,
TODAY() + 2 - Status: Not Started
- Subject:
-
6. Test it and activate it
Click Debug and run the Flow on a recent Task logged by Hublead, then Save it as LinkedIn conversation follow-up and click Activate. Sync a conversation on LinkedIn and check the record: the follow-up Task is there, due in two days.
Result
Each LinkedIn conversation synced to Salesforce now ends with a dated next step in the rep's task list, unless one is already open. Follow-ups stop depending on memory, and a manager can see which ones are overdue.
Stop copy-pasting LinkedIn into Salesforce
Create the Lead or Contact and its Account from the profile, and log the conversation as Tasks, without leaving LinkedIn.
Before you activate the Flow
Does it fire the moment a prospect replies?
It fires when the conversation is logged in Salesforce, which happens when the rep opens it on LinkedIn: automatically if auto-sync is on, or with the Sync messages button. There is no background sync on Salesforce, so a reply the rep has not opened has not reached Salesforce yet.
Why not one follow-up per message?
One sync can log several Tasks for the same person. The Get Records check keeps a single open follow-up per person, so the rep gets one task per conversation.
Can I send a notification instead of a task?
Yes. Create a notification type in Setup → Notification Builder → Custom Notifications, then replace Create Records with the Send Custom Notification action, with Recipient IDs set to a text collection variable that holds {!$Record.OwnerId}.
Does it work with LinkedIn invitations?
No. Invitations and InMails are not tracked on Salesforce today. The Flow runs on synced messages.
More workflows on LinkedIn activity
All playbooks →- WhenYou open a prospect on LinkedIn
- ThenAdd to the Campaign
- WhenA LinkedIn message is synced
- ThenGroup by rep and by week
- WhenLast LinkedIn Message Received before 21 days ago
- ThenSave view: Cooling LinkedIn leads
Put this workflow live
this week.
Install the extension, connect HubSpot or Salesforce, and sync a LinkedIn conversation: it lands on the CRM record, ready for this recipe.
Free to start, no card needed.