> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firsttouch.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For API operations, fetch https://gateway.firsttouch.ai/api/public/openapi.json for the complete input/output schemas, internal references, and x-mcp-annotations. Endpoint Markdown intentionally omits generated schema fragments. Select /api/public/tools/<tool_name> using the exact underscore-separated name. Send requests to https://gateway.firsttouch.ai; the canonical document currently omits servers. Start at https://docs.firsttouch.com/api-reference/agent-start.md.

# Workflow Actions

> Trigger First Touch flows automatically using HubSpot Workflows.

First Touch integrates with HubSpot's **Automation > Workflows** tool so you can trigger First Touch actions from HubSpot contact workflows.

> [!NOTE]
>
> Use First Touch actions in **Contact-based** HubSpot workflows. Do not assume Deal, Task, or Lead workflow support. 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](https://mintcdn.com/firsttouchinc/X5zSINWOosKihpV3/images/Workflow-image.png?fit=max\&auto=format\&n=X5zSINWOosKihpV3\&q=85\&s=968214a5415803ddcce989abc7440c1f)

**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.

| Action Name | Description & Configuration |
| :- | :- |
| **Enroll Contact into FirstTouch flow** | Sends the HubSpot Contact to the selected published FirstTouch Flow Plan. |
| **View profile** | Queues a Social profile view for the Contact. **Config:** choose a Social sender strategy. |
| **Send connection request** | Queues a Social connection request. **Config:** choose a Social sender strategy and optionally provide a connection note. When wait behavior is enabled, HubSpot can receive the **FirstTouch activities URL** and **Connection request result** outputs. |
| **Check connection status** | Checks the Contact against the selected Social sender. HubSpot can use **Is connected on Social** and **Connection check status** for later workflow decisions. |

> [!NOTE]
>
> 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.

Owner-based strategies match the respective HubSpot owner's email to an active Team member, not a saved mapping alone. The resolved sender needs a usable LinkedIn Connected Account with LinkedIn Profile Connections Sync completed.

## 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.

Connection requests enable best-effort withdrawal 30 days after actual execution, separately from the acceptance wait. Withdrawal is not guaranteed and can be skipped when account or invitation information is unavailable.

Unexpected asynchronous failures can remain in a repair window for up to two days by default before a failure result is delivered; recognized business failures bypass that window. A later workflow action can continue after FirstTouch confirms and records its predecessor's failure, reopening the workflow's Flow Enrollment when permitted. Failure alone does not guarantee continuation. Canceled enrollments and enrollments whose goal was achieved remain protected from later action additions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.