• About us
Log inDemo

Workflows

Give recurring work a path you can follow.

From a starting point to an outcome you can inspect.

Choose how the work starts

Start manually, on a configured schedule or from an incoming webhook. Pick the entry point the process actually needs.

From a starting point to an outcome you can inspect.

  1. Start manually, on a configured schedule or from an incoming webhook. Pick the entry point the process actually needs.

  2. Select tasks from your workspace catalog and pass the values each step needs. The available actions depend on your workspace configuration.

  3. Open a run to see its status and inspect its steps. When a task fails, use the execution details to understand where the process stopped.

A process is clearer when its inputs are explicit.

Give each step the information it needs, and keep the execution visible to the people maintaining the process.

See it on your own data

Named tasks

Select the tasks that exist in the workspace.

Step inputs

Bind the read output to the document task input.

Repeated steps

Inspect the outcomes for each supplied document.

Execution history

Read the failure detail before deciding on another run.

One engine, two very different processes.

Start with your unit of work and the tasks your workspace exposes. These examples illustrate configurations to review with your team.

See it on your own data

An event team prepares its documents

The input is an event: date, venue and guest count. A document task receives that event identifier. Review the resulting document before sharing it with the client.

A service team prepares a weekly review

The input is a reporting period. A scheduled process gathers the records needed for a review. The team decides what action follows from the result.

Read the process before you run it.

The editor brings the task sequence and its configuration into one place. Select a step to inspect its inputs, then use execution history to examine a run.

See it on your own data

Connect the work through the tasks in your workspace.

A workflow uses the actions its workspace exposes. Start with the records and documents your process already uses, then confirm the available task for each hand-off.

See it on your own data

Records into tasks

Use a business record as the input to a configured action.

Records into tasks

Tasks into documents

Pass the result to the next task when your document workflow provides it.

Tasks into documents

Triggers & Actions

Connect a defined event or schedule to explicit business actions.

Discuss your process

Approval Flows

Route a decision to the right reviewers and retain the approval outcome.

Discuss your process

Approval Flows

Route a decision to the right reviewers and retain the approval outcome.

Runs, Exceptions & Retries

Runs, Exceptions & Retries

Inspect execution outcomes, investigate failures and control subsequent retries.

Runs, Exceptions & Retries

  1. Inspect execution outcomes, investigate failures and control subsequent retries.

Questions about Workflows

Yes. Begin with a single process and the tasks available in your workspace. Confirm the required configuration with your team before relying on it operationally.

CRMManage the commercial relationship from first contact to qualified opportunity.ExploreProjectsCoordinate a delivery commitment through milestones and tasks while tracking its financial outcome.ExploreDocumentsOrganize files and their sharing lifecycle, including documents that need a signature.Explore

See Enobase on your operation.

30 minutes, your real events on screen. We'll show you exactly where Enobase saves your team time, no slides.

Have a quick chat
Solutions
  • Finance
  • Quotes
  • E-Invoicing
  • HR & Payroll
Industries
  • Catering
  • Construction Company
  • Private Equity
  • All industries
Platform
  • Data Model
  • Knowledge & Collaboration
  • AI & Workflows
  • Analytics
  • Integrations
Company
  • About us
  • Hiring policy
  • Press & Brand
  • Download
  • Privacy
  • Terms
  • Subprocessors

© 2025 Enobase, Inc. All rights reserved.

  • LinkedIn
  • X
  • GitHub
Actions
All
Automated
Needs review

Deal moved to Won

Kickoff task created and assigned to the CS team.

Invoice 32 days overdue

Reminder sent to the account owner automatically.

New message in #support

Ticket opened and routed to the on-call agent.

marketing/asset-workflow-node
family: asset; kind: canvas; frame: sticker; subject: an input binding; move: highlight the event identifier; neighbour: the run shows the resolved value; content: Build document, event identifier from Read event; props: task and input labels; not: an if/else branch; static: yes
Open asset editor
marketing/widget-workflow-run
family: widget; kind: run; frame: sticker; subject: per-item execution; move: highlight each input item; neighbour: a single run holds these executions; content: documents DOC-2026-0031 and DOC-2026-0032; props: item identifiers and outcomes; not: a performance benchmark; static: yes
Open asset editor
marketing/asset-activity-list
family: asset; kind: log; frame: sticker; subject: a failed task; move: expand its error detail; neighbour: the editor defines the task; content: Build document Failed, required event missing; props: status and error; not: a retry guarantee; static: yes
Open asset editor
marketing/widget-workflow-run
widget: marketing/widget-workflow-run family: widget kind: run frame: sticker subject: a proposed event document configuration move: show the selected step and its input, then its outcome; do not animate unsupported branching neighbour: the run history shows what happened; this slot explains the specific configuration or record described here content: EVT-2026-0142; Maison Delcourt; 18 Sep 2026; 80 guests; Prepare document; Review outside this workflow props: workflow name, task labels, input values and execution status not: an integration marketplace or an unrestricted if/else builder static: yes
Open asset editor
marketing/asset-activity-list
widget: marketing/asset-activity-list family: asset kind: log frame: sticker subject: a proposed weekly service review configuration move: show the selected step and its input, then its outcome; do not animate unsupported branching neighbour: the run history shows what happened; this slot explains the specific configuration or record described here content: Week of 07 Sep 2026; Atelier Renard; open jobs JOB-2026-0041 and JOB-2026-0042; reporting task availability to configure props: workflow name, task labels, input values and execution status not: an integration marketplace or an unrestricted if/else builder static: yes
Open asset editor
marketing/screen-workflow-lab
widget: marketing/screen-workflow-lab family: screen kind: screen frame: desktop subject: the workflow editor for a straight task sequence move: show the selected step and its input, then its outcome; do not animate unsupported branching neighbour: the run history shows what happened; this slot explains the specific configuration or record described here content: Prepare event documents; Manual start; Read event; Build document; inspector event identifier; execution history props: workflow name, task labels, input values and execution status not: an integration marketplace or an unrestricted if/else builder static: yes
Open asset editor
marketing/widget-workflow-run
family: widget; kind: run; frame: sticker; subject: a record task input; move: select the input; neighbour: document task consumes the result; content: customer CUS-2026-0017, configured record action; props: input identifier; not: an unconfigured integration; static: yes
Open asset editor
marketing/widget-workflow-run
family: widget; kind: run; frame: sticker; subject: a document task input; move: select the source record; neighbour: record task produces the input; content: document DOC-2026-0031, source EVT-2026-0142; props: identifiers; not: universal document automation; static: yes
Open asset editor
marketing/widget-contract-library
widget: marketing/widget-contract-library family: widget kind: record frame: sticker subject: Triggers & Actions move: Highlight the decision and its supporting source record neighbour: marketing/widget-contract-library content: Connect a defined event or schedule to explicit business actions.; illustrative scope, not verified production behavior props: Named record, owner, source reference and review outcome not: An assertion of automated behavior or product availability static: yes
Open asset editor
marketing/widget-contract-library
widget: marketing/widget-contract-library family: widget kind: record frame: sticker subject: Approval Flows move: Highlight the decision and its supporting source record neighbour: marketing/widget-contract-library content: Route a decision to the right reviewers and retain the approval outcome.; illustrative scope, not verified production behavior props: Named record, owner, source reference and review outcome not: An assertion of automated behavior or product availability static: yes
Open asset editor

© 2026 Enobase, Inc. All rights reserved.

Log in
All systems normal