Hello,
We have a sequence of emails with call task intervals (not pausing the sequence). We want our sales team to receive a call task for anyone who clicks on a link in the emails, but not pause the sequence.
Many thanks
Steven
Hi @SWard75 ,
The sequence itself cannot trigger a task based on a link click, but we can achieve this with a workflow. A thing to note is that the email would need to be a marketing email, as HubSpot can only track clicks in marketing emails. Unfortunately, for sales emails used in sequences, this is not possible.
Here are the steps to set up the workflow:
- Create a Contact-Based Workflow
- Set the Trigger
Add the filter: Marketing email > Email name > Clicked link in email.
Choose the specific email and link that should trigger the task.
-
Add the action Create Task and
Assign the task to the appropriate sales rep or team.
This setup will allow you to create tasks based on link clicks without interrupting the sequence flow, as it will not pause the sequence unless you add a delay action before the task action.
For your reference:
I hope this helps, feel free to mark it as the solution 
and give it an upvote 
! Let me know if you have further questions!
Hi @SWard75,
There are a few ways you can approach this, one would be using this beta:
Sequences
Dynamic Sequences
September 9, 2024
What is it?
Dynamic sequences are a new type of sequence that leads with automation and creates manual task steps only for contacts who are engaging with your initial outreach.
Why does it matter?
Today, sequencing is static. Every prospect enrolled gets the same experience: the same content, over the same channels, at the same pace.
Personalized, multi-channel outreach is known to perform better, but it’s time consuming and difficult to scale!
With dynamic sequences, reps can send personalized automated emails and prioritize manual outreach steps only for the contacts who are showing engagement.
This means reps are spending their time only on the contacts who are warmed up and more likely to convert!
How does it work?
Users will see a new option when creating a sequence: dynamic sequence.
Dynamic sequences start with a series of automated emails meant to warm up a lead. If that person opens an email more than once or clicks an email, the sequence will immediately switch to create manual tasks.
Within the builder, users can configure two paths within the sequence: one for automated outreach to the contact and a second path for the contacts who engage with the automated outreach. Within the rep-led path, users can configure what steps they’d like to execute when a contact engages with them.
Users can enroll contacts as usual - using automation or manually. Performance can be monitored within the performance tab of the sequence, including insights on every step of the sequence.
Who gets it?
Professional Customer Platform, Enterprise Customer Platform, Sales Pro, Sales Enterprise, Service Pro, Service Enterprise
Learn More:
Learn more on the Knowledge Base
You can find this beta here:
This essentially gives you a branch when a contact interacts with an email:
In a Professional subscription, your sequence would stop after the task creation however. This feature is currently in beta and you can give feedback in the top right corner directly:
I’d suggest doing so and maybe we’ll see exactly what you’re requesting.
If you’re on an Enterprise subscription, you could continue with the rest of the steps by creating a second sequence and using a workflow to enroll contacts into the sequences with the remaining actions: Enroll and unenroll contacts in sequences using workflows (The enrollment trigger would be the completion or creation of the task on the right.)
Without an Enterprise subscription, @CateDuarte proposed a nice approach in this thread.
Best regards!
Hi @SWard75 this needs testing but I would look for:
You’ll need to select Sequence enollment here
Testing is to understand if the email click is known will make it trigger anytime an email click is added.
@CateDuarte nice one! The amount of places where sequences can be referenced in filters (contact properties, event-based triggers, associated object) makes this easy to miss.