Triggers
Every workflow must have exactly one trigger node. The trigger defines what starts the workflow. Fluxlix supports five trigger types, covering automated event-driven execution, time-based scheduling, external webhooks, and interactive chat sessions.
Work Item Trigger
Fires when something happens to a work item in your project.
You can configure it to respond to specific events:
- A work item is created
- A work item's status changes (optionally filtered to specific from/to transitions)
- A work item is updated (any field change)
- A work item is assigned
The work item that caused the trigger is automatically available in the workflow as $task, giving you access to its fields, metadata, and related data.
When to use it: Automating responses to backlog activity — for example, kicking off an AI agent whenever a story moves to "Ready for Dev", or notifying a channel when a bug is marked "Critical".
Manual Trigger
Runs the workflow on demand. Manual triggers can be invoked from the project's workflow list, from a work item's action menu, or via the API.
You can define input parameters for a manual trigger so that the person (or system) running it can pass in values at execution time.
When to use it: One-off operations, testing, or workflows that should only run when explicitly requested rather than automatically.
Schedule Trigger
Runs the workflow on a repeating schedule using a cron expression.
# Run every day at 8am UTC
0 8 * * *
# Run every Monday at 9am UTC
0 9 * * 1
When to use it: Periodic tasks such as generating a weekly status report, syncing data from an external source, or running a health check on open work items.
Webhook Trigger
Exposes a unique HTTP endpoint that external systems can POST to in order to start the workflow. The incoming request body and headers are available as variables inside the workflow.
When to use it: Integrating with third-party services that support outgoing webhooks — for example, triggering a workflow when a CI pipeline finishes, when a new support ticket arrives, or when a form is submitted.
Chat Session Trigger
Starts the workflow when a user begins or continues a conversation in Fluxlix's chat interface. The conversation context, including prior messages and the user's current message, is passed into the workflow.
When to use it: Building interactive AI assistants that can answer questions, decompose requirements, or take actions on the user's behalf directly from within a chat session.