Workflow Generation¶
GloriaMundo turns natural language into an executable workflow you can inspect, edit, preview, and run. You describe the automation in plain English, and GloriaMundo proposes a workflow with the trigger, steps, and data flow laid out clearly before anything executes.
The “Propose, Then Approve” Loop¶
GloriaMundo is designed to move quickly without hiding complexity. Instead of asking many questions up front, it proposes a complete workflow and makes it easy for you to approve, edit, or ask for changes.
You’ll typically see:
- A workflow name and description
- A trigger (manual, scheduled, or webhook)
- A step-by-step plan
- Connection requirements (what needs to be connected to run)
From there, you can refine details conversationally (“use a different channel,” “add a filter,” “run it weekdays only”) or edit specific steps in the visual editor.
Chat vs. Build¶
In the builder, you can:
- Chat to clarify the goal or explore options without changing the workflow.
- Build to generate (or update) the workflow itself.
This separation helps keep the experience predictable: you can ask questions freely, and only “Build” when you want the workflow to change.
Workflow Modes¶
GloriaMundo offers multiple build modes designed for different situations (for example: fastest draft vs. more careful planning). In practice, this lets you choose whether you want a quick “good enough” plan to edit, or a more thorough first pass.
If you want a quick start, use a faster mode and rely on the visual editor to polish details. If you’re building something sensitive or multi-step, use a more thorough mode and lean on Virtual Run before executing.
Starting From A Demo Workflow¶
If you prefer to start from an example rather than a blank prompt, the builder includes demo workflows you can load onto the canvas. These act like templates: you can inspect the structure, then customize triggers, destinations, and connected services.
See Workflow Templates.
Adding Context (Projects, Documents, Links)¶
GloriaMundo supports “bring your context” workflow building:
- Projects let you group workflows by initiative, client, or team.
- Documents can be uploaded to a project and used as reference context when generating and refining workflows.
- Links you paste into the builder can be used as additional reference context while drafting a workflow.
This is especially useful for domain-specific workflows (sales playbooks, support macros, internal SOPs) where tone, terminology, and constraints matter.
See Knowledge Base for document details.
Connections And Service Selection¶
Workflows often require connected apps. When a workflow needs a service you haven’t connected yet, GloriaMundo will surface that requirement and guide you through connecting it.
Some capabilities can be fulfilled by multiple services (for example, “send email” or “post an update”). When there are multiple options, GloriaMundo can prompt you to choose your preferred service and remember that preference for future workflows.
See Connecting Services.
Writing Effective Prompts¶
The quality of generated workflows depends on how you describe your automation. Here are examples of effective vs. vague prompts.
Good Prompts (Specific and Actionable)¶
- ✅ Clear action (send Slack message) - ✅ Specific timing (every morning at 9am) - ✅ Defined data source (calendar events) - ✅ Clear trigger (new lead in HubSpot) - ✅ Multiple actions with clear order - ✅ Specific channels and services - ✅ Specific schedule (Friday 5pm) - ✅ Clear data to process (closed GitHub issues) - ✅ Defined output action (email team)Vague Prompts (Still Work, But May Need Refinement)¶
- System will propose a multi-channel marketing workflow - You may want to specify which channels (Twitter, LinkedIn, email) - System will ask what kind of automation (auto-reply, digest, forwarding) - Better: "Forward emails from VIP customers to #urgent Slack channel" - Too broad - which apps and what should happen between them? - Better: "When I star an email in Gmail, add it to my Notion reading list"Prompt Patterns That Work Well¶
| Pattern | Example |
|---|---|
| When X happens, do Y | "When a new subscriber joins, send them a welcome email" |
| Every [time], do X | "Every Monday morning, post our team metrics to Slack" |
| Take X from A and put it in B | "Take new Typeform responses and add them to Airtable" |
| Watch X for Y and alert Z | "Watch Twitter for mentions of my brand and alert me on Slack" |
| Summarize X and send to Y | "Summarize weekly GitHub activity and email the team" |
Step Types (At A Glance)¶
GloriaMundo workflows are built from step types that cover common automation needs, including:
- Connected-app actions (read and write operations in your tools)
- Content generation and transformation steps (summaries, classifications, formatting)
- Code steps for deterministic logic and data shaping
- Conditional steps for branching behavior
- Browser automation steps for web-based tasks when appropriate
You can inspect and edit steps in the Workflow Editor.
Troubleshooting¶
"The workflow didn't understand what I wanted"¶
Try being more specific about: - The trigger - When should this run? - The action - What exactly should happen? - The services - Which apps are involved?
"It's asking for a connection I don't want to use"¶
You can modify the workflow to use a different service, or connect the suggested service. If multiple services can satisfy a capability, choose the one you prefer in the connections flow.
"The generated steps don't match my expectations"¶
Remember the Glass Box principle: you see the workflow and can preview it before it runs. You can: 1. Ask for modifications ("change step 2 to use email instead of Slack") 2. Start over with a more specific prompt 3. Use a more thorough preset for higher-stakes workflows