Include Action — Reference
Execute an included module workflow in the surrounding action context.
Execute an included module workflow in the surrounding action context.
Before you begin
Section titled “Before you begin”- An open Server Connect action. Use disposable records/files when testing generated write or upload steps.
Include Action
Section titled “Include Action”Execute an included module workflow in the surrounding action context.
Fields or generated steps
Section titled “Fields or generated steps”| Part | Meaning |
|---|---|
| Action | Select the reusable module/action file under the modules picker. The serialized include is a module path; it is not an HTTP URL. |
Verification example
Section titled “Verification example”Create a small reusable module with a named Set Value output. Include it in a test action and verify where that output appears. Compare this with Exec Action when you need explicit parameters and a separately named library result.
What remains your responsibility
Section titled “What remains your responsibility”Include and Exec Action are different mechanisms. Include executes the selected module in the existing action context; Exec Action provides a library-call parameter/result boundary. An include can perform real side effects every time it runs, so do not treat it as merely loading documentation or metadata.
Review the resulting workflow
Section titled “Review the resulting workflow”Inspect the actual generated or included steps, their inputs and their final output before connecting the action to a user-facing page.
Check your result
Section titled “Check your result”You can identify what this editor entry adds and configure or interpret it without assuming an unfinished scaffold is a completed workflow.