Tasks (Scheduler)

Send an Email, SMS or Push campaign again and again on a cron schedule — the Tasks (Scheduler) module.

The Tasks module sends a campaign on a repeating schedule — every morning, every Monday, the first day of each month — without anyone pressing Send. A scheduled task holds a 5-field cron schedule (in UTC), the user it runs as, and an Email, SMS or Push campaign; each time the schedule fires, Norbix starts that campaign. To send one campaign once at a later time, use Send later on the channel's campaign page instead.

Enable the module

Open a project and choose Tasks in the left menu. While the module is off, Cloud shows the Norbix Tasks page; press ENABLE. You need a project role that can manage modules (the scheduler:manage permission, for example Owner or Administrator).

Tasks → enable page, shown while the module is off.

The enable page still says that only email campaigns work and that Push and SMS tasks are coming. That text is old: the task form offers Email, Push and Sms, and tasks of all three kinds were saved and ran on a test project on 2026-10-06.

After ENABLE, Cloud opens Scheduled Tasks (empty for a new project) and shows the Scheduler menu: Tasks and Settings.

After ENABLE: the Scheduled Tasks list and the Scheduler menu.

Turning the module on also starts again every task that was enabled when the module was last turned off. To turn it off, see Settings.

Module map

Screen	What it is for
Tasks	Every scheduled task of the project with its cron, channel and status: create, edit, disable or enable, delete.
Task run log	When each task ran and why a run failed — read in Logs → Logs, next to the campaigns each run started.
Settings	Turn the module off for the project; the tasks are kept.

Your first task

1. Get the channel ready — the module on, a provider and a template (Email, SMS or Push).

2. Create a service user with a role — the user the task runs as. Its role must let it read the template and send the campaign.

3. Create the task — name, cron, Run as user, Command (Email, Sms or Push) and the campaign.

4. Check the run — at the cron time a campaign appears in the channel's campaign list, and Logs shows Scheduler task ran.

Use it from code

Every Do it from code block in the Tasks pages uses this client. Install @norbix.ai/ts (see SDK install) and set NORBIX_API_KEY to a project API key.

import { Norbix } from '@norbix.ai/ts';

const projectId = 'pr_7ZX0qmmXY0AoSXi9GAITtr';
const norbix = new Norbix({ projectId }); // the key comes from NORBIX_API_KEY

await norbix.hub.scheduler.enableScheduler();
const { list } = await norbix.hub.scheduler.getSchedulerTasks({ pageSize: 20 });
console.log(list.items.map((t) => `${t.taskId} ${t.name} ${t.cron} ${t.type} enabled=${t.isEnabled}`));

The CLI lines use the generic norbix hub … commands of @norbix.ai/cli (signed in with norbix login, project id in NORBIX_PROJECT_ID):

norbix hub scheduler enable

The client sends the project id with every call (the norbix-project-id header), so the requests do not repeat it. The CLI does the same with the project of norbix login --project …, norbix config set projectId … or NORBIX_PROJECT_ID. The shorter norbix scheduler … commands work too, for example norbix scheduler list.

Related

Campaigns concept · Message templates concept · Permissions · Users · SDK · CLI · API