Workflows API Status
Understand the current public API boundary for Eigenn workflow definitions and executions.
Now, Eigenn public API v1 does not document an endpoint that does any of these operations:
- lists workflow definitions
- creates or updates a workflow
- triggers a workflow run
- lists executions
- resumes a workflow pause
There is no public workflows scope in the API-key scope list. The OpenAPI document has no /workflows path.
Use the Product Workspace
Build, check, and recover workflows from the Workflows product area.
The product can support workflow definitions, executions, and pauses. Those controls are not part of the public developer contract. Do not call private browser requests from an external integration.
MCP Boundary
The remote MCP endpoint gives scoped finance tools, resources, and prompts. It does not give public workflow-builder CRUD or execution-history tools.
An MCP client can prepare input for a workflow with the permitted customer, invoice, transaction, report, or search tools. It is not a supported workflow execution API.
Supported API Components
External services can use documented resources to prepare or reconcile workflow inputs:
Marketplace apps such as Zapier, n8n, or Make give app-specific automation connections. They do not create a general /workflows REST contract.
Check for Future Availability
Use the current OpenAPI document as the source of truth:
https://api.eigenn.io/v1/openapi
When workflow operations become public, look for the methods, schemas, necessary scopes, errors, and idempotency behavior. Confirm those details before an integration depends on them.
Migration from Legacy Examples
Legacy examples such as GET /v1/workflows, POST /v1/workflows, or POST /v1/workflows/{id}/runs are not present in public OpenAPI v1. Remove them from clients and tests.