Workflow Triggers
A trigger determines when a task runs. In GeniSpace, the trigger is set by the task's type, which you choose when you create the task. There are three task types:
| Task Type | Trigger | When it runs |
|---|---|---|
| Manual | Manual trigger | Only when you start it from the console |
| Event | Webhook | When an external system is configured to call the task's webhook |
| Scheduled | Cron schedule | Automatically, on the schedule you define |
You select the type in the task creation dialog (see Task Management for the full create-task flow). A task has exactly one type.
Manual Trigger
A Manual task runs only when you start it yourself. This is the simplest trigger and is well suited to on-demand jobs, testing, and workflows that need a human to kick them off.
Running a manual task
You can start a manual task in two places:
- From the task list: use the Run Now action on the task row.
- From the task editor: click Run Now in the top toolbar (save your changes first if prompted).
When you run the task, a parameter form appears so you can fill in the input parameters the workflow expects. After you submit, execution begins and you can follow the run in the bottom debug panel.
Manual runs are the easiest way to test a workflow while you build it. Run it, check the live logs, adjust the design, and run again.
Event Trigger (Webhook)
An Event task is intended to be started by an external system through a webhook. When you create an Event task, the task carries two webhook-related fields:
| Field | Description |
|---|---|
| Webhook URL | A URL associated with the task, generated by the system (read-only) |
| Secret Token | An optional secret you can set for verifying the request |
You configure these on the task, and use them when integrating a third-party system that needs to notify GeniSpace.
Event tasks are configured through the Webhook URL and Secret Token fields described above. Refer to your platform administrator or the API documentation for the exact request format your deployment expects when calling a task webhook.
Scheduled Trigger (Cron)
A Scheduled task runs automatically on a schedule you define with a Cron expression. Scheduling is handled by the croner engine.
Cron expression format
GeniSpace cron expressions use a 6-field format that includes a seconds field:
┌──────────── second (0 - 59)
│ ┌────────── minute (0 - 59)
│ │ ┌──────── hour (0 - 23)
│ │ │ ┌────── day of month (1 - 31)
│ │ │ │ ┌──── month (1 - 12)
│ │ │ │ │ ┌── day of week (0 - 7, where 0 and 7 are Sunday)
│ │ │ │ │ │
* * * * * *
Examples:
| Expression | Meaning |
|---|---|
0 0 9 * * * | Every day at 09:00:00 |
0 0 9 * * 1-5 | Monday to Friday at 09:00:00 |
0 */15 * * * * | Every 15 minutes |
0 0 0 1 * * | At midnight on the first day of every month |
The schedule is evaluated using the task owner's time zone.
The task creation dialog provides a visual builder to help you assemble the Cron expression, so you don't have to write it by hand.
Start and end date window
In addition to the recurring schedule, a scheduled task supports an optional active window:
- Start Date (required for scheduled tasks): the task will not run before this date.
- End Date (optional): the task will not run after this date.
The platform enforces this window when deciding whether to run the task: a scheduled task only runs while it is Active, has a valid schedule, the current time is on or after the start date, and (if set) on or before the end date. Once the end date has passed, the task stops being scheduled.
Choosing a trigger type
- Use a Manual task for on-demand jobs, ad-hoc reports, and anything that should be started by a person.
- Use an Event task when an external system should start the workflow via webhook.
- Use a Scheduled task for recurring work such as periodic reports, syncs, and clean-up jobs.
FAQ
Details
Can I change a task's trigger type after creating it?
The trigger is defined by the task type. Open the task in the editor and use Configure to edit the task properties, including its type and the schedule or webhook settings associated with it.Details
Why isn't my scheduled task running?
Check that the task Status is Active, that the Cron expression is valid, that the current time is within the start/end date window, and that the task has a workflow to run. A scheduled task that is inactive, expired (past its end date), or has no valid schedule will not run.Details
Do I have to provide parameters every time I run a manual task?
When you start a manual task, a parameter form appears for the inputs the workflow expects. Fill it in and submit to start the run.Next Steps
- Learn how to create and manage tasks in Task Management
- Explore the Workflow Builder to design your workflow
- Learn how to configure Environment Variables
- See the Workflow Overview for concepts and use cases