A
Alan Thomas
Feature request — a read scope for workflow definitions
The public API exposes workflow metadata (GET /workflows/, scope
workflows.readonly) but no read path to workflow structure: triggers, waits,
branches, and per-action configuration are not retrievable.
That gap blocks a category of legitimate third-party tooling — configuration
documentation, change auditing, QA review, and migration validation across
subaccounts. Agencies inheriting an account today have no supported way to
produce a written record of what a workflow actually does.
Requested: a documented, read-only endpoint returning workflow structure,
under a scope such as workflows.definition.readonly. Read-only is sufficient;
no write access is being requested here.
This is additive to the platform and benefits any developer building audit,
documentation, or migration tooling, not only us.