Settings
Configure ActionFlow metadata, active state, visibility, templates, transfers, and deletion while distinguishing enforced activation limits from configured plan values.
Settings
Settings is the flow-level configuration surface. Open it from Actionflow Studio or ActionFlow → Settings (/actionflows/{actionFlowId}/settings). Node inputs and credentials remain in Node settings.
General metadata
| Field | What it controls |
|---|---|
| Name | The label shown in the flow list and Actionflow Studio. |
| Description | Optional flow summary. The current settings form validates a maximum of 500 characters; treat that as a UI form limit, not a general runtime payload rule. |
| Category and tags | Catalog metadata used by templates, Explore, and organization views. |
| ID and slug | Generated identifiers; the form displays them as read-only values. |
Active and passive state
New ActionFlows are passive. Set a flow to active when it should be eligible for webhook and scheduled triggers.
- Passive flows remain editable and can be configured/tested in Actionflow Studio.
- The current webhook handler returns 409 with
Flow is passivebefore enqueue, and scheduled dispatch only claims active flows. - The API/Actionflow Studio
runActionFlowpath currently does not perform that active-state check, so do not expect a 409 from that path; passive is not a general execution lock. - Activating a flow also recalculates the next scheduled run time, so do not use activation as a way to edit the graph.
The active-flow count is enforced when activation changes a passive flow to active. The current activation path reads the CMS product.flowLimit value, rejects a value of 0, treats -1 as unlimited, and excludes templates from the active count. A plan can therefore prevent activation even when the graph itself validates.
Other CMS plan values are not all enforced by the same path. In particular, file-size and storage values can be displayed or used in the editor without being enforced by the current upload action. See Artifacts.
Visibility and templates
- Request a public listing for Explore, then unpublish it when it should no longer be listed.
- Mark a flow as an organization template so it can be used as a starting point in the template flows surface.
- Listing, template, transfer, and delete actions require the appropriate organization permissions. See Organization permissions.
These settings change how a flow is surfaced or copied. They do not change the execution semantics documented in Execution model.
Transfer and delete
Transfer moves a flow to another organization where the current user has the required permissions. Delete removes the flow from the organization. Both are destructive or ownership-changing operations, so confirm the destination and the flow before using them.