Configure and run actions
Configure registered actions and understand the effect of invoking them.
An action performs an operation through the storefront runtime. It may write data or call an external service. Content → Advanced → Actions shows available actions and saved configurations supplied by the site.
Configure an action
- Open Actions and select an available action or a saved block.
- Set its schema fields, or use the JSON editor when the site's inputs are freeform.
- Save an available action with a block name to reuse its inputs. A saved block autosaves field changes.
- Connect that configuration to the component or workflow that will call it, then publish the saved changes.
Saving a block records configuration; it does not execute the operation. Conversely, Run invokes the action against the preview target immediately. That invocation can have real effects on the service behind the preview, even before the site's content is published. Use inputs and an environment appropriate for the operation.
Inspect a result
When Run is available, inspect the structured response. Verify the intended external result rather than assuming that a successful HTTP response means the business operation completed.
Available inputs and permissions come from the registered action and runtime. If the action is missing or invocation is denied, ask a developer to check registration, schema, credentials, and access rules. The editor does not bypass authorization or make a private action public.
Implementation reference: Studio Site Editor. Reviewed 2026-10-05.