The active flag is a parameter on both creation and update, and test_workflow takes its own test data, so the path from draft to live never leaves the tools. When something stops firing, list_executions filters by workflow and by status, which is where the failure is identified rather than in the interface. Connections hold the credentials for the apps a workflow talks to, and the available-apps catalogue is what tells you which app keys exist to connect.
A client for a self-hosted Automatisch instance covering workflows, app connections and execution history.
- Workflows listed by status with a limit, fetched by ID, created, updated and deleted.
- An active flag set at creation or afterwards, so a workflow can exist before it is allowed to run.
- App connections listed by app key and created with their credentials, against the catalogue of available apps and their capabilities.
- Execution history filtered by workflow and status, and a test run against sample data you supply.
A running Automatisch instance, its address in AUTOMATISCH_BASE_URL, and an API key in AUTOMATISCH_API_KEY.
One command plus a key — npx -y automatisch-mcp-server, then supply credentials