FirstTouch has its own workflow builder, and HubSpot is optional. Choosing between HubSpot workflows, FirstTouch flows and agent workflows comes down to what drives your next action.
Choose by the situation
- Use HubSpot workflows when the actionable data is already in HubSpot or you need to coordinate multiple tools connected to it.
- Use FirstTouch flows when social signals drive the play or several team members need to coordinate their outreach.
- Use agent workflows when the next step depends on substantial, changing context, such as deal notes, conversation history and several signals considered together.
When a social signal needs an agent
A buyer comments on your executive's post. If the rep and executive already know who should follow up and in what order, use a FirstTouch flow. If the team needs deal notes and past messages to decide whether to reach out, what to say or who should respond, use an agent to propose the next step.
HubSpot workflows for CRM data or connected tools
Imagine a webinar follow-up process. Registration and qualification data already live in HubSpot, and the play involves FirstTouch plus other tools connected there.
Start the wider process in HubSpot. Its workflow can use that CRM data to trigger FirstTouch enrollment while coordinating the other connected tools. You keep the orchestration close to the information that starts the play.
Choose HubSpot when CRM data drives the next step, or when several connected tools need to participate. Either reason can make it a good fit.
FirstTouch flows for social signals or coordinated team outreach
Imagine supporting a rep's outreach with connections and messages from an executive and another teammate. Each person has relevant contacts at the same target account.
Use FirstTouch flows to coordinate connections and messages from multiple members within the same Flow. This brings the team's social outreach into one play.
Choose this route when actionable social data drives the next step, or when the complexity comes from coordinating several people. It works whether or not HubSpot is part of your setup.
Agent workflows for decisions that need more context
Imagine deciding how to follow up on an active opportunity. The answer depends on deal notes, a long conversation and several recent signals. A single field or trigger does not tell the whole story.
Use an agent to consider that context together and direct supported FirstTouch actions through MCP or the HTTP API. Signal stacking means weighing several signals together when deciding what to do next.
Choose this route for the judgment the play needs. Give the agent context it is authorized to use and choose the review controls for your workflow.
A play can use all three
For a hypothetical target-account campaign, HubSpot could select accounts using CRM data and coordinate connected tools. FirstTouch flows could manage the rep and executive's social outreach. An agent could consider deal notes and conversation history when proposing the next step.
Choose a clear owner for each handoff so the routes work toward the same play. Available actions, review controls and CRM sync depend on your configuration and access.
Frequently asked questions
Does FirstTouch have its own workflow builder?
Yes. FirstTouch flows is its own builder for outreach and follow-up, including social-led and multi-team plays.
Is HubSpot required?
No. HubSpot is optional. Use it when your actionable data is there or your process needs to coordinate tools connected to HubSpot.
Can we combine all three?
Yes. HubSpot can start FirstTouch enrollment, and agents can direct supported FirstTouch actions. Define the handoffs, intended senders and review responsibilities for your specific play.
Choose the right route for one real play
Bring the data, team members and tools involved. Book a demo to work through the choice.
