Before the first flow of a company can be created, the tenant must already have a logo on file — without it, creation returns a 404 error.
The createButtonLabel field is not accepted on POST /v1/flows — it belongs to the start form, not to the flow. Use createCardLabel instead.
The flow's color field accepts either a hexadecimal code (#RRGGBB) or one of 7 fixed named values (turquoise, blue, orange, violet, pink, purple, light_blue). The color of each labelOptions item, however, must always be a hexadecimal code — named values are rejected on that specific field.
Omitting createCardLabel or cardCountLabel on an update does not raise an error — the API silently resets those fields to their default values, with no warning. This is the only case in this domain where a missing field does not return an explicit error.
GET /v1/flows returns the list of flows inside items, with no pagination metadata (no cursor or total count).
Deleting a flow (DELETE /v1/flows/{id}) is a destructive and irreversible operation — it removes phases, cards, and all associated configurations.
Adding a user to a flow requires the full canonical payload {users:[{userId, userName, userEmail, role:{id, name}}]} — simplified shapes such as {userId, roleId} are rejected with a 400 error.
dynamic-fields-paths is the reference catalog for building trigger conditions, rules, and templates — each path already comes with its expected type (array, text, currency, date, boolean, or number).
