Skip to main content
First Touch integrates with HubSpot’s Automation > Workflows tool so you can trigger First Touch actions from HubSpot contact workflows.
Use First Touch actions in Contact-based HubSpot workflows. Make sure the Flow Plan or Connected Account needed by the action is already available to your Team before configuring the HubSpot step.

​
Setting up an Action

1

Create a Workflow

In HubSpot, navigate to Automation > Workflows and create a Contact-based workflow.
2

Add an Action

Click the + (plus) icon to add a step.
3

Select First Touch

In the side panel, scroll down to the “Integrated apps” section and select First Touch.Selecting First Touch in HubSpot Workflows
4

Configure Action

Choose one of the available actions (detailed below).
  • For enrollment: Select the First Touch flow you want HubSpot to send contacts into.
  • For LinkedIn custom actions: Select a sender strategy. If you choose manual, you must also choose the LinkedIn account to use.
  • For connection requests: You can optionally supply the note that First Touch should use for the request.
5

Save

Click Save. When the workflow runs, First Touch will process the contact according to the selected action.

​
Available Actions

You can mix and match these actions inside HubSpot workflows.
LinkedIn message and InMail workflow actions are not part of the documented production action set. Do not design a workflow around an action that is not present in your HubSpot portal.

​
Sender Strategy Options

Some First Touch custom HubSpot actions support sender selection strategies.
  • By HubSpot company: First Touch selects a sender using the HubSpot company relationship.
  • By HubSpot contact: First Touch selects a sender using the HubSpot contact owner.
  • Manual: You choose the LinkedIn account explicitly for the action.

​
Wait and Result Behavior

Only actions that show output fields in HubSpot return values for later workflow steps. Use wait behavior only when the action exposes a result that a later HubSpot step needs. Queuing an action does not guarantee that the underlying outreach has completed unless the configured wait behavior says it waits for completion. If multiple First Touch native action cards run in the same workflow path, the first card that creates the flow enrollment sets the enrollment priority. Later cards do not override that priority.