Pipelex × AmbactiBring Pipelex into
the flow of work.
A little less busywork with Pipelex.
Other operations4 capabilities+
- Start a pipeline and wait for its result
Start a durable run and poll internally until it finishes — paste your method + inputs, run, get the result. If Max Wait is exceeded, returns the pipeline_run_id to fetch later.
- Start a pipeline
Start a durable run and return immediately with its pipeline_run_id (no waiting) — collect the result later with Poll & Get Result or Get Run Result, even from another workflow
- Poll a run until its result is ready
Wait for an already-started run by its pipeline_run_id: poll until it finishes or Max Wait is exceeded (then returns a "still running" output, not an error)
- Get a run result
Fetch a run result once by its pipeline_run_id (no polling) — returns status RUNNING while still in flight, the result when completed
Frequently asked
questions.
What could an Ambacti integration do with Pipelex?
The documented operations include Start a pipeline and wait for its result; Start a pipeline; Poll a run until its result is ready; Get a run result.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Pipelex?
Decide which work could run on its own and which steps need your review.