GoHighLevel Task Completed Trigger: Setup Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 23 October 2026 · 9 min read
The GoHighLevel Task Completed trigger is one of the quietest triggers in the Workflow builder, and one of the most useful. It lets the moment a team member ticks off a task become the starting gun for whatever should happen next, without anyone remembering to do it.
This guide walks through how a HighLevel task completed workflow is set up, where it fits alongside the other triggers in our workflow-trigger series (Contact Created, Pipeline Stage Changed, Call Status, Email Events and more), and how to build it so it fires cleanly every time.
Quick Facts
| What fires it | A task for the contact is marked completed |
| Where you set it up | Automation > Workflows, by adding the Task Completed trigger |
| Main filter | Assigned User (run different workflows depending on who completed the task) |
| Sibling trigger: Task Added | Fires when a task is created for the contact |
| Sibling trigger: Task Reminder | Fires when a task's reminder time is reached |
| Source | HighLevel Help Centre, 2026 |
What the GoHighLevel Task Completed trigger actually does
According to the HighLevel Help Centre's list of workflow triggers (2026), Task Completed fires when a task for the contact is marked completed. That is the whole definition, and its simplicity is the point.
Because tasks are attached to contacts, the workflow that starts has the contact in hand. Every action you add afterwards (send an email, update a field, move an opportunity, notify a colleague) runs against that same contact record.
Think of tasks as the human checkpoints in your process. Most automation is triggered by something the customer does. This trigger is different: it is triggered by something your team does, which makes it the bridge between manual work and automated follow-through.
If your team already lives in the task list, our guide to managing team workload with GoHighLevel Tasks covers how to keep that list organised before you start automating off it.
Task Completed vs Task Added vs Task Reminder: which task trigger fits?
HighLevel gives you three task-related triggers, and they are designed to work together rather than compete. Choosing the right one depends on which moment in a task's life you care about.
| Trigger | Fires when | Best used for |
|---|---|---|
| Task Added | A task is created for the contact | Alerting the assignee, logging that work has started, setting a "work in progress" tag |
| Task Reminder | A task's reminder time is reached | Nudging the assignee, escalating to a manager if the task is still open |
| Task Completed | A task for the contact is marked completed | Kicking off the next step: client emails, stage moves, field updates, review requests |
A tidy pattern is to use all three across one process. Task Added tells the team member there is work, Task Reminder chases it, and Task Completed hands the baton to automation once it is done.
How to set up a HighLevel task completed workflow, step by step
HighLevel's Task Completed help article (2026) says you set it up under Automation > Workflows by adding the trigger. Here is the full build sequence we use with clients.
| Step | What to do | Why it matters |
|---|---|---|
| 1 | Go to Automation > Workflows and create a new workflow from scratch | A clean workflow is easier to test than a cloned one with leftover actions |
| 2 | Click Add New Trigger and choose Task Completed | This is the event that starts the workflow |
| 3 | Rename the trigger to describe the business moment, e.g. "Onboarding call task done" | Future you (and your team) will know what it is for at a glance |
| 4 | Add the Assigned User filter if the workflow should only run for specific team members | Stops a sales workflow firing when a support rep closes a task |
| 5 | Add an If/Else condition on contact tags, pipeline stage or custom fields where needed | Narrows the workflow to the right contacts without relying on filters that do not exist |
| 6 | Build the actions that should follow the completed task | This is the payoff: the next step happens automatically |
| 7 | Check the workflow settings, including Allow Re-entry | Controls whether the same contact can run through more than once |
| 8 | Save, publish and test with a test contact | Confirms the workflow fires and every action behaves as expected |
Using the Assigned User filter
The Help Centre lists Assigned User as the main filter on this trigger. In practice that means you can run different workflows depending on which team member completed the task.
That is handy when roles are clearly split. Your sales closer completing a task can trigger a proposal follow-up, while your onboarding specialist completing a task can trigger a welcome sequence. For the broader picture of how trigger filters behave, see our guide to GoHighLevel workflow trigger filters.
Why task naming conventions make or break this trigger
Here is the catch most people miss. Because the main filter is Assigned User, the trigger itself does not neatly separate "discovery call done" from "send contract done" when the same person owns both tasks.
If one team member completes many different kinds of tasks, a single Task Completed workflow with only an Assigned User filter will fire for all of them. The fix is a process decision, not a technical one.
Keep task titles consistent
Agree on a short, fixed set of task titles per process and stick to them. Consistent titles make reporting cleaner, make handovers easier, and make it far easier to reason about what the workflow will do.
- Prefix titles by process, such as "ONB – Kickoff call" or "SALES – Discovery call".
- Create tasks from workflows or templates rather than typing them freehand.
- Document the approved titles in your team SOP so new staff use the same wording.
Narrow the workflow with If/Else on contact data
Rather than relying on task details the trigger may not filter on, use workflow If/Else branches on contact information you control: tags, pipeline stage, or custom fields. For example, only send the onboarding recap if the contact carries an "onboarding-active" tag.
A reliable approach is to set a tag or field when the task is created (via the workflow that creates it), then check for it in your Task Completed workflow. Test carefully whenever you lean on task-specific signals, and confirm in your own account what data is available before building logic around it.
Practical use cases for the Task Completed trigger
The best uses share one trait: a human has to do something first, and only then should automation take over. These are the builds we see deliver the most value.
Onboarding checklist handoffs
When your onboarding lead completes the kickoff call task, the workflow can create the next task for the build team, email the client a summary of what happens next, and tag the contact so the right nurture sequence starts.
Sales call follow-up
When a rep marks the discovery call task complete, send the prospect a recap and a clear next step, such as a booking link or proposal. The follow-up goes out while the conversation is still fresh, not three days later.
Job completion to review request
For trades and service businesses, a "job complete" task is the natural moment to ask for a review. Add a short wait so the customer has time to settle, then send the request by SMS or email.
Internal QA and notifications
Completed tasks can alert a manager to check the work, or post a heads-up to the team. Our guide to internal team notifications via Slack, email and SMS covers the notification actions in detail.
Move the opportunity stage
When the "proposal sent" task is completed, move the opportunity to the matching stage automatically. That keeps your pipeline honest, and it can in turn kick off anything built on the Pipeline Stage Changed trigger.
Update a "last task done" custom field
Create a custom field such as "Last task completed" or "Last task date" and populate it with the Update Contact Field action. It gives you a quick at-a-glance status on the contact record and something reliable to filter Smart Lists on.
Testing your workflow and guarding against re-entry
Before you trust any Task Completed workflow with real clients, test it end to end. Create a test contact, assign a task to the right user, mark it complete, then check the workflow's execution history to confirm every action ran.
- Test once with the correct Assigned User and once with a different user to confirm the filter works.
- Test with a contact that fails your If/Else condition to confirm the branch stops correctly.
- Check that emails and SMS render properly with real contact data.
- Re-open and complete the same task again to see how re-entry behaves.
That last point matters. The Allow Re-entry setting decides whether a contact can go through the workflow more than once. If a contact will legitimately have many completed tasks over time, re-entry is usually needed; if the workflow sends a one-off message, leaving it off protects clients from duplicates.
Where you do allow re-entry, add a guard. A simple approach is to check a tag or custom field at the start and exit if the contact has already received that step.
Common mistakes to avoid
- Building one catch-all Task Completed workflow that fires for every task a user closes, then wondering why clients get the wrong email.
- Letting the team type task titles freehand, so nothing about your process is consistent or reportable.
- Assuming the trigger offers filters beyond Assigned User instead of using If/Else on tags, fields or pipeline stage.
- Turning on Allow Re-entry without a guard, so contacts receive the same message more than once.
- Skipping a proper test with a test contact and only discovering problems when a real client complains.
- Using Task Completed when the real moment you care about is the task being created or overdue, which is what Task Added and Task Reminder are for.
If you want a task-driven workflow system built for your team, book a strategy call with the HL Growth Partner team.
Frequently asked questions
When does the GoHighLevel Task Completed trigger fire?
According to the HighLevel Help Centre (2026), the Task Completed trigger fires when a task for the contact is marked completed. The workflow then runs against that contact, so every action that follows uses their record.
Where do I set up a HighLevel task completed workflow?
You set it up under Automation > Workflows by creating or opening a workflow and adding the Task Completed trigger. From there you add any filters, conditions and actions, then publish.
What filters are available on the Task Completed trigger?
HighLevel's help article lists Assigned User as the main filter. That lets you run different workflows depending on which team member completed the task. For anything more specific, use If/Else branches on tags, custom fields or pipeline stage inside the workflow.
What is the difference between Task Added, Task Reminder and Task Completed?
Task Added fires when a task is created for the contact, Task Reminder fires when a task's reminder time is reached, and Task Completed fires when the task is marked completed. Many teams use all three across one process: alert, chase, then hand off to automation.
How do I stop the workflow running for the wrong kind of task?
Keep task titles consistent, create tasks from workflows rather than freehand, and set a tag or custom field when the task is created. Then check for that tag or field with an If/Else at the start of your Task Completed workflow.
Should I turn on Allow Re-entry?
It depends on the workflow. If a contact will complete many tasks over time and each should trigger the same follow-up, re-entry is usually needed. If the workflow sends a one-off message, leave it off or add a tag-based guard to prevent duplicates.
How do I test a Task Completed workflow safely?
Create a test contact, assign a task to the right user and mark it complete. Then review the workflow's execution history to confirm each action ran, and repeat with a different user and a contact that fails your conditions.
Related Articles on HL Growth Partner
More workflow triggers
- GoHighLevel Call Status Trigger: Setup Guide
- GoHighLevel Opportunity Status Changed Trigger
- GoHighLevel Email Events Trigger: Setup Guide
Contact and team automation
- GoHighLevel Assign To User: Contact Owner Rules
- GoHighLevel Contact Changed Trigger: Setup Guide
- GoHighLevel Update Contact Field Action: Workflows
