Can it watch the run and fetch outputs?

Yes. Use --watch to stream the execution, and --output or --output-all to download results once the run finishes.

What does --ci change?

In CI mode, in-progress executions stop when the CLI is forcefully stopped. Without it, the CLI asks for confirmation before cancelling.

How do I scale the run?

Set --machines to a count, or pass --max for the maximum number of machines. Combine with --fleet and --use-static-ips when placement matters.

How does authentication work?

Pass a Trickest token with --token or --token-file so automated contexts can drive runs without interactive login.

Updated Jul 15, 2026

Utilities

Start a saved workflow from CI or a schedule

Start a Trickest workflow run from the command line.

Trigger a workflow from automation Control run scale and placement Chain one workflow into another

overview

What trickest-execute does

trickest-execute starts a saved Trickest workflow by --url or --workflow, passes --input key=value pairs, and can download named --output files when the run finishes.

Reach for it from CI, a scheduler, or another graph when the editor should stay out of the path. --ci stops in-progress executions if the CLI is interrupted. --create-missing provisions space and project paths that do not exist yet.

Pair with trickest-output when you only need results from runs that already finished. This node launches. That one retrieves.

source github.com/trickest/trickest-cli

use cases

Where trickest-execute fits

Trigger a workflow from automation

Reference a saved workflow by URL or by space, project, and name, pass inputs as key=value pairs, and run it from CI or a scheduler without opening the editor.

Control run scale and placement

Set the machine count or request the maximum, pick a fleet, and use static IPs so the execution provisions exactly the resources the job needs.

Chain one workflow into another

Run a workflow as a step inside a larger pipeline and download its outputs so a downstream node consumes the results.

Run unattended with CI mode

Enable CI mode so in-progress executions stop cleanly when the CLI is interrupted, keeping automated runs from leaving orphaned executions behind.

reference

trickest-execute inputs and flags

21 inputs

Name	Type	Flag	Description
url	STRING	--url	URL referencing a workflow, project, or space.
workflow	STRING	--workflow	Workflow name to execute.
input	STRING	--input	Input to pass as key=value, repeatable.
fleet	STRING	--fleet	Fleet to run the workflow on (default Managed fleet).
machines	STRING	--machines	Number of machines to use for the execution (default 1).
output	STRING	--output	Output to download when the execution finishes, repeatable.
watch	BOOLEAN	--watch	Watch the execution as it runs.
ci	BOOLEAN	--ci	Run in CI mode so interrupted CLI stops in-progress executions.

Showing key inputs. trickest-execute exposes 21 inputs in total.

Full flag reference (21 inputs)

Name	Type	Flag	Description
ci	BOOLEAN	--ci	Run in CI mode (in-progreess executions will be stopped when the CLI is forcefully stopped - if not set, you will be asked for confirmation)
max	BOOLEAN	--max	Use maximum number of machines for workflow execution
url	STRING	--url	URL for referencing a workflow, project, or space
fleet	STRING	--fleet	The name of the fleet to use to execute the workflow (default "Managed fleet")
input	STRING	--input	Input to pass to the workflow in the format key=value (can be used multiple times)
space	STRING	--space	Space name
token	STRING	--token	Trickest authentication token
watch	BOOLEAN	--watch	Watch the execution running
config	FILE	--config	YAML file for run configuration
output	STRING	--output	Output to download when the execution is finished (can be used multiple times)
project	STRING	--project	Project name
machines	STRING	--machines	The number of machines to use for the workflow execution (default 1)
set-name	STRING	--set-name	Set workflow name if it's imported from the library
workflow	STRING	--workflow	Workflow name
output-all	BOOLEAN	--output-all	Download all outputs when the execution is finished
token-file	FILE	--token-file	Trickest authentication token file
api-endpoint	STRING	--api-endpoint	The base Trickest platform API endpoint. (default "https://api.trickest.io")
create-missing	BOOLEAN	--create-missing	Create space and project if they don't exist
use-static-ips	BOOLEAN	--use-static-ips	Use static IP addresses for the execution
node-dependency	FILE	--node-dependency	This flag doesn't affect the execution logic of the CLI in any way and is intended for controlling node execution order on the Trickest platform only.
include-primitive-nodes	BOOLEAN	--include-primitive-nodes	Include primitive nodes in the workflow tree

example

Run trickest-execute

trickest-execute · command

# trickest-execute: run a workflow with domain input and watch progresstrickest execute --space demo --project recon --workflow subdomain-enum --input domain=example.com --machines 2 --watch --ci

sample output

example.comwww.example.comapi.example.commail.example.comstaging.example.comdev.example.comvpn.example.comcdn.example.com

guidance

Choosing trickest-execute

Use when you need to start a workflow programmatically from CI, a schedule, or another workflow. Prefer trickest-output when the run already finished and you only need its files.

trickest-output

Downloads results from existing runs. Use it when you need outputs, not a new execution.

trickest-cli

Full CLI this node wraps. Use it directly for listing, importing, and managing workflows beyond execution.

faq

trickest-execute questions

Pass a URL with --url, or name the space, project, and workflow. Add --input key=value pairs, repeatable, to supply the workflow inputs.

Run trickest-execute yourself

A workflow reference feeds trickest-execute, which runs the workflow on the platform and writes its outputs as a downloadable folder.

Open trickest-execute in the library Build a workflow with it

Facts on this page come from the live Trickest tool library.