Signal type
Define the kind of input the route accepts: customer update, support issue, or team brief. A run must match the workflow’s selected signal type before it can proceed.
VAELORA / PRODUCT
Coordinate signals, review gates, and execution routes.
Get early accessWorkflow anatomy
Vaelora’s current workflow runner coordinates internal task creation. A user starts each run and can inspect the resulting record.
Define the kind of input the route accepts: customer update, support issue, or team brief. A run must match the workflow’s selected signal type before it can proceed.
Choose the responsible team and task priority. These choices are recorded with the run so the resulting action has an explicit destination and level of urgency.
Require a review gate when a person should decide whether an action proceeds. A pending run creates no task until approved; rejecting it records the decision without creating work.
An approved run, or a route without a review gate, creates a tracked task inside Vaelora. The task contains the signal context, workflow name, owner, priority, and a suggested due date.
Each run records its input, routing decision, review state, and task-creation result. This is an application activity record, not a certified compliance log.
Create a route, enable or disable it, and remove routes that are no longer needed. Disabling a workflow prevents new runs through it while past run records remain available.
Example routes
These examples illustrate internal coordination rather than external service execution.
A revenue owner receives a customer-update signal. The workflow pauses for approval, then creates a follow-up task when a reviewer accepts it.
A support-issue signal routes to Support at the chosen priority. A route without a review gate immediately creates an internal investigation task.
A team brief routes a checklist action to Product or Operations. Use a review gate if readiness needs a decision before the task should be created.
Practical questions
No. Included workflow actions create tasks inside Vaelora. Email, chat, CRM updates, and other external actions require separate integrations and explicit authorization.
The current runner starts when an invited user submits a signal. It is not a background monitoring or scheduling service.
The run is marked rejected and a rejection entry is added to its history. No task is created for that rejected run.
Only a run awaiting approval can be approved. Once completed or rejected, its approval action is no longer available in the interface.