VAELORA / PRODUCT

Every handoff, intentional.

Coordinate signals, review gates, and execution routes.

Vaelora workflow conceptGet early access

Workflow anatomy

A route with an owner and a checkpoint.

Vaelora’s current workflow runner coordinates internal task creation. A user starts each run and can inspect the resulting record.

01

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.

02

Owner and priority

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.

03

Approval policy

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.

04

Internal action

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.

05

Run history

Each run records its input, routing decision, review state, and task-creation result. This is an application activity record, not a certified compliance log.

06

Workflow controls

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

Choose where judgment belongs.

These examples illustrate internal coordination rather than external service execution.

01

Customer renewal / review first

A revenue owner receives a customer-update signal. The workflow pauses for approval, then creates a follow-up task when a reviewer accepts it.

02

Support triage / direct task creation

A support-issue signal routes to Support at the chosen priority. A route without a review gate immediately creates an internal investigation task.

03

Launch readiness / accountable handoff

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

Know what to expect.

Will a workflow email customers or update my CRM?

No. Included workflow actions create tasks inside Vaelora. Email, chat, CRM updates, and other external actions require separate integrations and explicit authorization.

Do workflows run automatically in the background?

The current runner starts when an invited user submits a signal. It is not a background monitoring or scheduling service.

What happens if I reject an action?

The run is marked rejected and a rejection entry is added to its history. No task is created for that rejected run.

Can approval happen more than once?

Only a run awaiting approval can be approved. Once completed or rejected, its approval action is no longer available in the interface.