Skip to content

Capabilities

This page is a plain-language tour of what your workflows can do in GloriaMundo. It covers the kinds of work a workflow can carry out, how workflows can be started, the range of apps you can connect to, the practical limits to design within, and the preview system that lets you trust a workflow before it acts.

What your workflows can do

A workflow is a sequence of steps, and each step performs one kind of work. You can combine the following capabilities in a single workflow.

  • Connect to and act on apps. Send a Gmail message, post to Slack, append a row to Google Sheets, create a HubSpot contact, and so on. Each action runs against an app you have connected.
  • Reason and generate with AI. Summarise content, draft text, classify input, and make decisions based on context using a language model.
  • Read images and documents. Describe what is in an image, read the text out of a scanned page or screenshot with OCR, and parse PDFs. Text-based PDFs have their text read directly, and scanned or image-only PDFs are read page by page with vision.
  • Pull structured data out of text. Turn unstructured text, email bodies, or extracted document content into clean structured fields and rows for later steps to use.
  • Run code. Execute custom Python in a secure, isolated sandbox for data transformation, calculations, or logic that is easier to express as code.
  • Search the web and X. Query the public web for current information, and search X (Twitter) with native data access.
  • Read a specific web page. Fetch a given URL and extract its readable content.
  • Branch on conditions. Route the workflow one way or another, or skip steps, depending on a condition.
  • Iterate over lists. Repeat a set of steps once for each item in a list that is resolved while the workflow runs, with several items processed at a time.
  • Delegate to sub-agents. Hand a focused sub-task to a child workflow that works on it independently, optionally running several in parallel and combining their results.
  • Save files to connected apps. Generate a file in text, Markdown, CSV, HTML, or JSON and write it to Google Drive, optionally emailing it through Gmail.
  • Remember state across runs. Store and retrieve values that persist between runs, so a scheduled workflow can track a counter, a timestamp, or the last item it processed.

GloriaMundo can also generate images. This runs through the platform's model routing rather than as a workflow step you place yourself.

For step-by-step configuration of each of these, see Step Types.

How workflows start

Every workflow has a trigger that decides when it runs. There are four shapes.

  • Run manually. You start the workflow on demand from the builder.
  • On a schedule. The workflow runs on a recurring schedule, for example every morning or once an hour.
  • Via webhook. An inbound HTTP request starts the workflow, so another system can fire it.
  • When something happens in a connected app. The workflow runs in response to an event in a service you have connected, for example a new file landing in a Google Drive folder, an email arriving, or an issue being opened on GitHub.

See Scheduling & Triggers and Event Triggers for setup detail.

Connecting to apps

GloriaMundo connects to 1,000+ apps through Composio, with managed OAuth. You authorise GloriaMundo through each app's own login page, and your workflows can then read from and act on those apps. For the list of available apps and how connections work, see Available Integrations.

Glass Box preview

Before a workflow runs for real, you can preview it with Virtual Run. Every step is shown before it acts, so you see exactly what each step will do.

Steps that only read data run live during the preview, so the data you see is real and current from your connected apps. Steps that would create, modify, or send anything are previewed only and cause no side effects. Because each step is laid out before it touches anything live, you can stop a workflow that is about to do the wrong thing, for example a connection behaving unexpectedly, before any real action happens.

This is what lets you trust running any of the 1,000+ available integrations: you do not have to take a workflow's behaviour on faith, because you can see each step before it acts. For the full explanation, see Virtual Run (Preview).

Limits and quotas

The following limits are worth knowing when you design a workflow. Values shown as a default can usually be adjusted within the stated range.

Area Limit
Workflow size No fixed cap on the number of steps; workflows can be large.
Sub-agent nesting depth Up to 10 levels deep.
Sub-agent budget $1.00 by default per sub-agent, up to a maximum of $100.
Parallel sub-agents Up to 100 child sub-agents running in parallel.
Iteration concurrency 1 to 25 items processed at a time per loop, 5 by default.
Iteration size Up to 1,000 items by default, 10,000 maximum.
App action timeout 5 to 300 seconds, 30 seconds by default.
Browser step timeout 1 to 120 seconds, 30 seconds by default.
Code step timeout 30 seconds.
Schedule frequency A scheduled workflow can run at most once every 5 minutes.
Saved state 100 keys per workflow, 64 KB per value, kept for 90 days by default (adjustable from 1 to 365 days).