Start
The Start block is the entry point for every workflow in MindStudio.
Define how and when a workflow is triggered
The Start block is the entry point for every workflow in MindStudio. It specifies the invocation method — how the workflow gets launched — and is always the first block in any workflow chain. The run mode you select determines what triggers the workflow and what data is available when it begins executing.
The block supports several run modes: on-demand (a user manually triggers the workflow), workbench (for testing and development), schedule (CRON-based timed execution with a timezone and cron expression), email (an inbound email to a dedicated address triggers the workflow), extension (a Chrome browser extension triggers the workflow based on the currently open page), webhook (a POST to a dedicated URL triggers the workflow), and packaged workflow (invocation from another MindStudio agent or an MCP service). Each mode has its own configuration options, such as approved sender lists for email mode, enabled sites for extension mode, a secret for webhook mode, and full input/output schema definitions for packaged workflow mode.
For modes other than on-demand and workbench, the Start block accepts launch variables — named key-value pairs passed in at invocation time that downstream blocks can reference. Scheduled runs also support static variable values defined directly in the schedule configuration. Because the Start block produces no output variables of its own, its primary role is to initialize the workflow context and pass control to the next connected block.
What you can build
Real-world workflows powered by the Start block.
Scheduled Report Generation
Trigger a workflow automatically on a recurring CRON schedule to generate and distribute reports at defined intervals, with static launch variables supplying configuration parameters.
Inbound Email Processing
Launch a workflow whenever an email arrives at a dedicated address, automatically populating sender, subject, and message body as launch variables for downstream processing.
Webhook-Driven Automation
Invoke a workflow via a POST request from an external platform such as Zapier or Make.com, passing structured data as launch variables to drive the workflow logic.
Browser Extension Workflow
Trigger a workflow from a Chrome extension that automatically supplies the current page URL, metadata, full page text, and any user-selected text as launch variables.
On-Demand User Workflow
Allow a user to manually start a workflow by pressing a button, with subsequent User Input blocks collecting any data needed before processing begins.
Agent-to-Agent Invocation
Configure a workflow as a packaged workflow so it can be called by another MindStudio agent or an MCP service, with defined input and output schemas enabling structured data exchange.
Ready to add Start to your workflow?
Get Started FreeCommon questions about Start
What are the available run modes for the Start block?
The Start block supports seven run modes: onDemand, workbench, schedule, email, extension, webhook, and packagedWorkflow. Each mode determines what triggers the workflow and what configuration options are available.
What are launch variables and when should I use them?
Launch variables are named keys (defined as an array of objects with a key property) that receive values passed in at invocation time. They are used when the run mode is anything other than onDemand or workbench. For on-demand workflows, use a User Input block to collect data instead. For workbench mode, use Set Variable blocks.
Does the Start block produce any output variables?
No. The Start block has no defined output fields. Its role is to initialize the workflow and pass control to the next connected block, with any incoming data available through launch variables.
How does the schedule run mode work?
In schedule mode, you define one or more schedule entries, each with a standard cron expression, a timezone, a text description, an active flag, and an optional set of static launch variable values. MindStudio manages the scheduling and triggers the workflow according to the cron expression.
What is the packagedWorkflow run mode used for?
The packagedWorkflow mode allows the workflow to be invoked by another MindStudio agent or an MCP (Model Context Protocol) service. It requires defining metadata (name, description, icon, help text, and transition type) along with explicit input and output schemas so the calling agent or service knows what data to send and expect in return.
Related capabilities
User Input
Prompt the user for one or more pieces of data that will be saved as a variable. Can include text, multiple choice, images, or files.
Run Function
Execute a custom JavaScript or Python function
Chat
Start a chat session with an LLM.
End
End the workflow. Optionally return a structured output (for API) or send notifications.
Jump
Transition to another workflow, maintaining the same scope
Menu
Present the user with a menu and transition to the next step based on their choice
Add Start to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.