e-volv

Workflows

Wire data between steps without code

Pass data through workflows using template variables. Reference the event that fired the workflow, the output of any previous step, or static node configuration, no bespoke glue code required.

What it does

  • {{trigger.*}} for event payload fields
  • {{outputs.<step-id>.*}} for previous step results
  • {{config.*}} for node-level constants
  • Variable picker with autocomplete in every template field

The rest of Workflows

  1. Visual builderReact Flow canvas with trigger, agent, git, CI, ticket, and approval nodes aligned to the 22px grid.
  2. Ticket nodesCreate, update, comment, read, and list tickets as first-class workflow steps across Jira, Linear, and ClickUp.
  3. Reusable blocksSave a group of steps as a workflow block and reuse it across workflows.
  4. Dry-run testingRun the whole graph against sample trigger data with side effects stubbed out.
  5. AI generationGenerate a complete workflow (nodes, edges, and config) from a plain-English prompt.
  6. Execution engineTopological scheduling, parallel branches, step retries, and live SSE streams.

Try it on your own repository

A free workspace reaches everything above that is not marked opt-in.

Start freeBack to the register

We use only essential cookies to keep you signed in and the app working. With your consent we may enable optional analytics to help us improve e-volv. See our Privacy Policy and Terms.