Custom Workflows

Workflows are background automation pipelines that process events and generate insights. They're registered in the database and can be toggled globally (by system admins) and per-workspace (by workspace admins).

How workflows work

Each workflow has:

• Slug — Unique identifier (e.g., issue-processing)
• Queue — BullMQ queue name for job processing
• Triggers — Events that start the workflow (create, update, schedule, manual)
• Configuration — Per-workspace settings via a JSON schema

Enablement resolution

Enhance checks workflow enablement in this order:

1. If alwaysEnabled is true — workflow is always on (no override possible)
2. If globalEnabled is false — workflow is off system-wide (admin kill switch)
3. If a workspace override exists — use the workspace-specific setting
4. Otherwise — use the workflow's defaultEnabled value

Visibility flags

Flag	Description
hidden	Never shown in workspace settings UI (system-internal)
public	Visible to all workspace members (if false, admins only)
togglable	Workspace admins can enable/disable it
alwaysEnabled	Cannot be disabled per-workspace

Managing workflows

Workspace settings

Go to Workspace Settings > Workflows to see all available workflows. For each workflow, you can:

• Toggle it on/off (if togglable)
• Configure per-workspace settings (if configurable)
• View the workflow description and trigger types

Per-workspace configuration

Some workflows have configurable settings stored as JSON. For example, the issue processing workflow allows configuring the scoring model, similarity thresholds, and skip conditions.

Configuration schemas are defined per-workflow and validated on save.

Current workflows

Workflow	Slug	Triggers	Default
Issue Processing	issue-processing	Create, update, comment, batch, manual	Enabled
Daily Summary	daily-summary	Scheduled (6 AM UTC), manual	Enabled