Summary
Workflows triggered and watched from where the decision is made.
The gap in most automation platforms sits between deciding a process should run and going to the console to run it. Launch takes a payload and returns an instance ID, and the status call closes the loop without leaving the conversation.
What it is
A control surface for the Procesio automation platform: browse the process templates in your account, read one in detail, launch an instance of it with a payload, and check where that instance got to.
What you get
- The process templates listed, with page number and page size
- One template's full configuration, by its UUID
- An instance launched with an optional payload, synchronous or not, debug mode, a timeout in seconds and a connection ID
- Instance status for a running or completed run
- An authentication check that returns the current user's details
Requirements
A Procesio API key and its paired value in the environment, with the account username and password still read for the initial check. A .env file in the project root is the documented route.