HighLevel published a changelog update for Todoist: Workflow actions & triggers. Todoist is a task-management platform used by teams and individuals to organize work into projects, sections, and tasks, with support for labels, priorities, due dates, deadlines, comments, and collaboration.
What changed
Todoist is a task-management platform used by teams and individuals to organize work into projects, sections, and tasks, with support for labels, priorities, due dates, deadlines, comments, and collaboration.
The Todoist integration brings these primitives into the Workflow Builder so task-lifecycle activity fires customer-facing automations, and any workflow can manage Todoist tasks and projects without leaving the builder.
Why it matters for agencies and VAs
Agencies and VAs are usually the first people asked why a screen changed, why a workflow loads differently, or whether a new setting should be adopted. Tracking this early keeps client support, SOPs, and implementation calls cleaner.
How to use it
Open the affected HighLevel feature and confirm how the change behaves in a real sub-account.
Update any client-facing SOP, Loom, or checklist that mentions the old behavior.
Flag the change only for clients whose workflows, calendars, payments, sites, conversations, SaaS, or AI setup are affected.
Certified GHL Admin operator take
As a Certified GHL Admin, my read is simple: do not treat this as trivia. If the feature is part of a client fulfillment path, test it once, document the operational impact, then decide whether it deserves a client note or an internal-only SOP update. Source category: automations.
Frequently asked questions
What is the Todoist: Workflow actions & triggers update?
Todoist is a task-management platform used by teams and individuals to organize work into projects, sections, and tasks, with support for labels, priorities, due dates, deadlines, comments, and collaboration.
Why should agencies and VAs care?
HighLevel product changes can affect client SOPs, support replies, implementation calls, and QA checklists. Operators should know what changed before clients ask.
Where did this update come from?
It came from the official HighLevel changelog RSS feed hosted on the HighLevel ideas and changelog site.