Compare Hublead, Surfe and FirstTouch for three jobs: saving LinkedIn prospects to HubSpot, keeping CRM data current and starting follow-up from a profile.
To follow up with webinar registrants in HubSpot, trigger on Contrast registration, check the LinkedIn connection in FirstTouch, then message or send a request.
By Jared MintzlaffTo build a webinar registration follow-up workflow in HubSpot, trigger a contact-based workflow on Contrast's registration event, add FirstTouch's Check connection status action, then branch: existing LinkedIn connections enroll in a Flow Plan with a message step, and those not connected get a connection request. FirstTouch is the HubSpot-native execution layer for LinkedIn outreach and tracking: its action cards run inside your workflow and need a HubSpot Pro plan (Sales, Service or Marketing Hub). FirstTouch also has its own workflow builder, Flows, so HubSpot is optional.
You need a HubSpot Pro plan, FirstTouch and Contrast connected to HubSpot, a published FirstTouch Flow Plan for the message path and contact owners who can send. For an owner to send, their HubSpot email must match an active FirstTouch team member with a connected LinkedIn account and completed LinkedIn Profile Connections Sync.
The finished workflow is one trigger, one connection check and a three-way branch, so each registration sends the contact down exactly one path.
| Path | Action on that path | What happens next |
|---|---|---|
| Connected | Enroll Contact into FirstTouch flow, pointed at a Flow Plan with a message step | The contact owner's message sends from the Flow Plan (Step 5) |
| Not connected | Send connection request with a note naming the webinar | The workflow ends after the request (Step 4) |
| None met | A HubSpot task or internal email | The owner or RevOps reviews the contact (Step 3) |
Last updated: November 2026.
Start the workflow from Contrast's Webinar Registration event so each new registrant enrolls when HubSpot records the registration. Use a contact-based workflow, because FirstTouch documents its action cards for contact-based workflows only.
In the HubSpot workflow builder, open the trigger card and choose "When an event occurs." Search the criteria list for "Contrast" and select "Contrast webinars: Webinar Registration" from the App events section, then choose the "has been completed" event. Leave the frequency as "any number of times, anytime" so a later registration re-triggers the follow-up.

If that event is missing from your trigger list, check the Contrast connection. A registration trigger reaches people before the session, which suits a note asking what they want covered. For a touch after the session, the same pattern works on attendance data, as our guide on using HubSpot workflows to turn CRM data into LinkedIn outreach explains.
Check connection status tells the workflow whether the registrant is already a LinkedIn connection of the sender, and that answer decides which path they take. Set the sender to the contact owner so the check tests the person who will do the outreach.
Click the plus icon below the trigger and search for "FirstTouch" among the integrated apps. Select "Check connection status." Set the Sender field to "Contact owner," which FirstTouch's workflow action docs call the By HubSpot contact strategy, then save.

Branch on the Connection check status output so Connected and Not connected registrants take separate paths. HubSpot sends any record that matches neither branch to None met and ends the workflow for a record on a path with no actions, so put a review step on None met.
Click the plus icon below the Check connection status card and choose Branch, then "One property or action output." Select "Connection check status" from the Check connection status action's output. Set Branch 1 to "is equal to" "Connected," then add a second branch set to "is equal to" "Not connected."

Under None met, add HubSpot's Create task or Send internal email notification action so the owner or RevOps sees the contact. When someone lands there, start with FirstTouch's HubSpot troubleshooting checks for the sender and the contact's identity data.
On the Not connected path, use FirstTouch's Send connection request action from the contact owner, with a note that names the webinar. FirstTouch's docs allow notes of up to 300 characters and require LinkedIn Premium or Sales Navigator on the sender's account. An otherwise eligible account without either can send the request with no note.
Under the "= Not connected" branch, add a FirstTouch "Send connection request" action. Set the Sender to "Contact owner." In the Connection note field, insert the "First Name (Enrolled contact)" token, then the "Webinar Name" token from the Contrast integration, and type your copy around them. A note like this fits: "Hey [First Name], thanks for registering for [Webinar Name]! Do you have any questions or topics you'd like to see covered on the webinar?" The 300 characters include the inserted values, so test your longest webinar name.
Set "Wait for action completion" to the Yes option that pauses the workflow until the request is sent, then set "Wait for connection acceptance" to the No option that continues once the request is sent.

With those settings the workflow ends once the request is sent, so an acceptance triggers nothing further. If you want a message after acceptance, enroll this path in a Flow Plan instead, with a connection request and a message on its Accepted path. Unaccepted requests can be auto-withdrawn, with a 30-day default.
On the Connected path, add FirstTouch's Enroll Contact into FirstTouch flow action and point it at a published Flow Plan with a message step. FirstTouch's documented HubSpot workflow actions do not include a Send Message card, so the LinkedIn message runs from the Flow Plan.
Build the Flow Plan in FirstTouch first:
Back in HubSpot, under the "= Connected" branch, add the FirstTouch "Enroll Contact into FirstTouch flow" action, select that Flow Plan and save.
Decide how the webinar name reaches the message, because the Webinar Name token comes from the Contrast event and FirstTouch's HubSpot variables read contact and company properties. The easiest setup gives each webinar its own Flow Plan, with the name typed into the message. For one plan across a series, copy the name into a custom contact property before the enroll card, if HubSpot's Edit record action offers that token in your portal, then insert that property in the message.
The workflow stays off until you click "Review and turn on" in the top right, which is your last check before live registrants enroll. Confirm the sender on each action, match the branch values to the Connection check status output, proofread the note and message, and confirm the Flow Plan is published with your approval setting and enrollment mode.
Keep approval on for the message step during the first webinar so you can read the first messages yourself, then relax it if the copy holds up.
Approvals are on by default and configurable by action type, so a message goes out without review only if your settings allow it. Supported completed activity logs to the HubSpot timeline when Engagement Tracking is on and a HubSpot contact is matched, and FirstTouch keeps its own activity history either way.
Set the message step's approval rule in the Flow Plan, and send a test contact through the connection request card to see how your team's approvals treat it. Approval tasks appear in FirstTouch, reach mapped members as Slack direct messages once Slack is connected, and can sync as HubSpot tasks when task sync is enabled and company context and owner mapping exist. Both LinkedIn actions run when the sender's work schedule, daily capacity and approval settings allow, so the follow-up may not land right after someone registers.
"I've bootstrapped to a combined $30M+ ARR running a social first GTM strategy on LinkedIn and FirstTouch allows us to trigger, track, and attribute on it just like we do with email."
Adam Robinson, CEO, RB2B, quoted on the FirstTouch homepage
Build this play outside a HubSpot workflow when your HubSpot plan has no workflow action cards, when social signals drive the follow-up, or when several teammates need to coordinate their outreach. FirstTouch's own Flows builder covers those cases, and it works without HubSpot.
Assign an owner before the Check connection status step, because the action picks its sender from the contact owner. HubSpot's Rotate record to owner action can do this on Sales Hub or Service Hub Professional or Enterprise. Test one unowned contact before you turn the workflow on.
With the frequency set to any number of times, HubSpot enrolls the contact again and the check runs again, so someone who accepted the first request can land on Connected. FirstTouch's Re-enroll action is blocked after a completed LinkedIn message in that enrollment, so use a separate Flow Plan for each webinar if repeat registrants should hear from you again.
Yes, if registrations reach HubSpot as something a contact-based workflow can trigger on, such as a form submission or list membership. Swap the trigger and write the webinar name into your copy.
FirstTouch is $99 per sender per month with 500 credits per sender per month pooled across the workspace, and a 14-day free trial with no credit card. A sender is one connected LinkedIn account, and sending connection requests and messages uses no credits. HubSpot and Contrast are priced separately.
Build this on one upcoming webinar first. Start a free trial, or get a demo if you want to see the action cards and Flow Plans before you build.
Operationalize social inside HubSpot. Action and report on it, just like email.
Start free trialfirsttouch.com and getcontrast.io
Compare Hublead, Surfe and FirstTouch for three jobs: saving LinkedIn prospects to HubSpot, keeping CRM data current and starting follow-up from a profile.

Send LinkedIn from Salesforce by hand with Sales Navigator, via an outreach tool's sync, or from a Flow with FirstTouch for Salesforce (beta January 4, 2027).

Five ways to log LinkedIn activity to Salesforce: by hand, Sales Navigator writeback, extensions, outreach tools, and FirstTouch (beta opens January 4, 2027).
We use cookies to give you the best online experience. Find out more in our cookie policy.