Run Packaged Workflow
The Run Packaged Workflow block executes a packaged workflow — referred to in MindStudio as a "custom block" — from within a larger workflow.
Execute a packaged workflow as a reusable custom block
The Run Packaged Workflow block executes a packaged workflow — referred to in MindStudio as a "custom block" — from within a larger workflow. It works by referencing a source app and a specific workflow within that app, then passing inputs into that workflow and receiving outputs back. This makes it possible to invoke pre-built, self-contained logic as if it were a native block in the editor.
The block is configured with an app ID pointing to the packaged workflow's source application, a workflow ID identifying which workflow to run, and two variable maps: one for input variables passed into the packaged workflow and one for output variables that capture the results. A display name and icon URL are also stored for presentation purposes in the editor. The transition behavior can be set to either controlled or dynamic depending on how the block should hand off to the next step.
This block is the underlying mechanism that powers all custom blocks in MindStudio, including those available through MindStudio's Standard Library. From a workflow builder's perspective, packaged workflows appear and behave like any other block, but behind the scenes they are always executed through this wrapper. It fits into any workflow where reusable or shared logic needs to be invoked — such as standardized data transformations, common API call patterns, or shared prompt chains used across multiple applications.
What you can build
Real-world workflows powered by the Run Packaged Workflow block.
Reuse Shared Prompt Chains
Invoke a centrally maintained prompt workflow from multiple applications, ensuring consistent AI behavior without duplicating logic across projects.
Apply Standard Data Transforms
Run a packaged data formatting or normalization workflow as a step inside a larger pipeline, passing raw input and receiving structured output.
Integrate Standard Library Blocks
Use MindStudio's Standard Library packaged workflows — such as utility or helper blocks — by wrapping them through this execution mechanism.
Modular API Call Patterns
Encapsulate a common external API interaction in a packaged workflow and call it from any application that needs the same integration.
Shared Classification Logic
Execute a packaged classification or routing workflow to categorize inputs consistently across different workflows and applications.
Cross-App Workflow Composition
Reference a workflow from a separate source app by its app ID and workflow ID, composing complex behavior from independently maintained components.
Ready to add Run Packaged Workflow to your workflow?
Get Started FreeCommon questions about Run Packaged Workflow
What are the required parameters for this block?
The block requires an app ID identifying the source application of the packaged workflow, a workflow ID specifying which workflow within that app to run, an input variables map for passing data into the workflow, and an output variables map for capturing the results. A display name and icon URL are also part of the configuration but are used for presentation in the editor only.
What does this block return?
The block returns output through the output variables map defined in its configuration. The specific variables returned depend on what the referenced packaged workflow produces and how the outputVariables mapping is set up.
What kinds of workflows commonly use this block?
Any workflow that needs to invoke reusable or shared logic benefits from this block. Common scenarios include workflows that call Standard Library blocks, workflows that share common data transformation steps across multiple applications, and workflows composed from independently maintained packaged components.
How does this block relate to custom blocks in MindStudio?
This block is the underlying execution wrapper for all custom blocks in MindStudio. When a packaged workflow appears as a block in the editor, it is being run through the Run Packaged Workflow mechanism, which handles referencing the source app and workflow and managing input and output variable exchange.
What is the transitionType parameter used for?
The transitionType parameter controls how the block hands off execution after it completes. It can be set to either 'controlled' or 'dynamic', determining whether the transition to the next step follows a fixed path or is determined at runtime.
Related capabilities
[YouTube] Search Trends
Retrieve trending videos on YouTube by category and region.
[Facebook] Scrape Posts for Page
Get all the posts for a Facebook page
Run Connector from MindStudio Connector Registry (MSCR)
Run a raw API connector to a third-party service
Check App Role
Check whether the current user has a specific app role and branch accordingly.
Track Website Changes
Detect changes to a website
Add Run Packaged Workflow to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.