GoHighLevel Ask AI Scheduled Tasks: Setup and Traps

Ask AI in GoHighLevel is no longer just a chat box you type a prompt into and read an answer from. Since August 2026 it has a Task Scheduler: turn any Ask AI prompt into a recurring job that runs on its own, hourly, daily, on weekdays, weekly, once at a set time, or on a custom cron schedule, across web and mobile. For an agency running the same handful of prompts across a dozen sub-accounts by hand every morning, that is a real time save. It also ships with a few defaults that will surprise you if nobody reads the fine print first.

This article is about Task Scheduler specifically, the recurring-job layer inside Ask AI itself. It is not the Workflow AI Assistant (the contextual help and workflow-explainer tool inside the workflow builder), and it is not the AI Agent workflow action that calls Claude, Gemini or GPT from inside an automation. Task Scheduler runs independently of workflows entirely; you write a prompt in Ask AI, tell it when to run, and it runs whether or not any workflow is involved.

What Task Scheduler actually does

Any prompt you can type into Ask AI can be scheduled instead of run once. HighLevel’s own setup guide describes it as running in the background on a repeating cadence and saving the result each time, the same way a manually triggered Ask AI request would, just without you sitting there to trigger it. Think of prompts like “summarize this week’s new leads and flag any that have gone quiet” or “pull yesterday’s missed calls and draft a follow-up message for each” running on their own every morning, per sub-account, without a workflow being built for it.

Who can actually use it

Access follows Ask AI itself. Per HighLevel’s own Task Scheduler article (checked October 17, 2026), Ask AI is available to Agency Admins and Users, and to Sub-account Admins and Users, on the Unlimited AI Employee plan, and Scheduled Tasks follows the same availability: if you can open Ask AI in an account and see the Scheduled Tasks area, you can use Task Scheduler there. So the plan question is really the Ask AI question, and it matters if you are about to tell a client this feature is included in their setup.

One point the official documentation does not spell out clearly: whether that plan requirement applies per sub-account or across the whole agency account. Do not assume either way. Check the actual entitlement in your own dashboard, on the specific sub-account you plan to use it on, before promising a client a recurring report you are not sure the plan actually unlocks.

Setting up a scheduled task

From inside Ask AI, a prompt can be saved with a schedule attached rather than run immediately. The frequency options break down differently depending on where you are working:

That cron option is worth flagging on its own. HighLevel’s documentation mentions that cron scheduling exists for advanced timing patterns, but does not publish the actual syntax, valid field ranges, or a single worked example anywhere in its current support materials. If you plan to use it, treat the field as genuinely undocumented: test a cron expression on a low-stakes prompt first and confirm it fires when you expect, rather than assuming standard five-field cron syntax will behave exactly as it would in a Linux crontab.

The trap: nothing tells you it ran

This is the detail most likely to bite an agency that sets a task up once and walks away. Per HighLevel’s own support article, quoted directly: “By default, Task Scheduler focuses on running the prompt and saving the result. Notifications or emails only occur when your prompt explicitly instructs Ask AI to send them.”

In practice, that means a scheduled task with a prompt like “check the pipeline for stalled opportunities” will run every day, quietly produce a result, and never tell anyone it did. Nobody gets pinged. Nothing shows up in an inbox. The output sits wherever Ask AI stores it until someone remembers to go look. If the point of the task was early warning on a stalled deal, a schedule with no notification instruction defeats the entire purpose without ever throwing an error.

• If you want to be told, the instruction has to live inside the prompt text itself — something like “email me a summary of the results at the end of this response” or “notify me if you find any opportunity untouched for more than 5 days.”
• A prompt with no such instruction is a silent report generator, not an alert system. Decide which one you actually need before scheduling it.
• This applies the same way across every frequency — hourly does not add a notification any more than weekly does. The default is silence regardless of how often it runs.

The billing gotcha: every run counts

HighLevel’s documentation is explicit that a scheduled run is not a lighter-weight background process: “Each scheduled execution is effectively an Ask AI session under the hood and contributes to your AI usage just like a manually triggered Ask AI request.” An hourly task fires 24 times a day, and each of those firings draws down AI usage exactly as if a person had typed the prompt in by hand 24 times.

For an agency managing AI usage or credits across many sub-accounts, that turns scheduling frequency into a real cost lever, not just a convenience setting. Before defaulting every recurring prompt to hourly because it sounds more thorough, weigh whether the task actually needs that cadence, or whether daily or weekly gets the same operator value at a fraction of the usage draw — especially once you are running several scheduled tasks per sub-account across a full client roster.

Mobile is behind desktop, on purpose for now

Task Scheduler reached the GoHighLevel mobile app in version 4.22.0 and up, but HighLevel’s own changelog is upfront that mobile shipped a narrower version. The five frequencies in the table above (manual, hourly, daily, weekdays, weekly) are what mobile supports today; advanced custom schedules are explicitly listed as a planned future enhancement, not a current gap you are missing by mistake. The same changelog entry lists push and in-app completion notifications as planned rather than shipped on mobile as of this writing.

The practical implication: if you or a client-facing team member needs to set up or adjust a cron-based schedule, or wants to see a real-time push notification the moment a task finishes, do that from desktop for now. Mobile is fine for the common cadences and for checking that a task is still active, not yet for the advanced configuration end of this feature.

Editing a task and reading its run history

Two operator-level behaviors are worth knowing before you lean on this for anything client-facing. First, editing a scheduled task while a run tied to the old configuration is still in flight does not create a duplicate or a race condition: HighLevel’s documentation states that “pre-update background jobs that might conflict are gracefully skipped, preventing duplicate runs during the changeover.” You can safely adjust a prompt or its schedule without worrying that both the old and new version will fire on top of each other.

Second, Task Scheduler keeps a run history that logs failed and skipped executions with detail, which is useful for debugging why a report did not show up. But a manual “Run now” does not reset or shift the next scheduled fire time. If a daily task is set to run at 8am and you manually trigger it at 2pm to check the output, the next automatic run still happens the following 8am, not 24 hours after your manual test. Assuming otherwise is an easy way to end up with two runs close together and think the scheduler is misbehaving when it is not.

Where this actually earns its keep

The clearest use case for an agency is turning Ask AI into an unattended monitoring layer per sub-account, without building a workflow for it: a daily prompt that summarizes new leads and flags stalled opportunities, a weekly prompt that checks for missed calls with no follow-up logged, or an hourly prompt watching a specific pipeline stage during a launch window. None of that requires touching the workflow builder at all — it is Ask AI doing recurring analysis work on a schedule, which is a genuinely different operational pattern from either a workflow trigger or a one-off chat question.

Before rolling this out across client sub-accounts, work through this short checklist:

1. Confirm the sub-account is actually on the Unlimited AI Employee plan — check the dashboard directly rather than assuming based on the agency’s overall plan.
2. Decide, per task, whether you need a silent report or an alert, and if it is an alert, write the notification instruction into the prompt text itself.
3. Pick the loosest frequency that still does the job. Hourly should be a deliberate choice, not a default, given that every run draws AI usage.
4. If you need a custom cron schedule, test it on a low-stakes prompt first since the syntax is not documented, and do the setup from desktop rather than mobile.
5. Do not rely on “Run now” to reset a schedule, and check the run history rather than assuming silence means failure — silence by default is expected behavior, not a bug.

None of this makes Task Scheduler complicated. It makes it a feature with real defaults worth reading once, rather than a button you flip on and trust to behave the way a workflow trigger would.

Frequently Asked Questions

Do I need a specific GoHighLevel plan to use Ask AI Scheduled Tasks?

Yes. HighLevel's own documentation says Ask AI is available to Agency Admins/Users and Sub-account Admins/Users on the Unlimited AI Employee plan, and Scheduled Tasks follows the same availability: if you can open Ask AI in an account and see the Scheduled Tasks area, you can use it there. Whether the plan applies per sub-account or across the whole agency isn't fully spelled out, so check the actual sub-account you plan to use before relying on it.

Will a scheduled task notify me automatically when it runs?

No. By default it only runs the prompt and saves the result, with no notification or email sent. You have to write the notification instruction into the prompt text itself, such as asking it to email you a summary.

Does an hourly scheduled task cost more than a daily one?

Yes, in terms of AI usage. Each scheduled execution counts as a full Ask AI session against your usage, the same as a manually triggered request. An hourly task runs, and draws usage, 24 times a day.

Can I set up a custom cron schedule for a recurring Ask AI prompt?

Desktop supports an advanced/custom option described as cron-based, but HighLevel has not published the exact syntax or examples. Test any cron expression on a low-stakes prompt first. On mobile, advanced custom schedules are listed as a planned feature, not yet available.

If I manually run a scheduled task early, does that reset its next scheduled run?

No. A manual 'Run now' does not shift or reset the next automatic fire time. A daily task set for 8am still fires at the next 8am regardless of when you last triggered it manually.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.