A workflow is a set of steps GlideOS runs automatically at a cadence you choose. You describe the process you want handled, GlideOS turns it into named steps and deploys it. Workflows can run on a set schedule, when another system sends a request, when something happens in a connected service, or whenever you manually start one.

Workflows read and write the same project data your apps use. Every workflow in a project is listed under Workflows in the sidebar.

Building Workflows

Creating a workflow

To build a workflow, describe the process in the chat. GlideOS creates steps for each part of the process, names each step, and stores the workflow to the project.

Changing a workflow works the same way. Describe what you want different and GlideOS updates the steps and the workflow for you.

Disabling a workflow

Disabling stops a workflow entirely. Open the menu beside Run and choose Disable workflow.

A disabled workflow shows a banner reading This workflow is disabled — triggers won’t fire and manual runs are disabled. Steps, triggers, and run history are all preserved. To enable the workflow again, select Resume on the banner or in the menu.

Deleting a workflow

To delete a workflow entirely, open the menu in that workflow and select Delete.

The Workflow Screen

You can open a workflow screen from any project screen, or from the sidebar if the workflow is in your recent or favorited projects.

The workflow name sits at the top, with a line under it telling you when the next run happens. When no trigger is turned on, that line reads Runs on demand.

Run starts a run now, regardless of when the triggers are set.

The menu beside Run holds the controls for the workflow as a whole.

Output provides an overview of what the workflow produces.

Definition lists the steps in order, each with a name and a sentence about what it does. Steps that pause carry a label showing how long they wait, and steps that only happen under certain conditions are labeled as conditional.

Triggers

Triggers start workflows. A workflow can have more than one, and each one is listed in the Triggers section with its own on/off toggle. The fastest way to create new triggers is to ask GlideOS in the Chat. You can also click + to add a new trigger from the Workflow screen.

You can manually build two types of triggers from the Workflow screen.

Schedules

A schedule runs the workflow on a repeating clock. Choose how often it repeats, the time of day, and the time zone.

Webhooks

A webhook lets another system start the workflow by sending a POST request. GlideOS generates the address for you when you add the trigger.

The token inside that address is the only credential, so treat the address as a secret. If it gets out, regenerate it, which breaks any source still using the old one.

For extra security, you can turn on the secret header. GlideOS generates a secret value, and requests then have to include it in a header or as a bearer token. Requests without it are rejected. Regenerating the secret breaks senders still using the old one and leaves the address unchanged.

Turning a trigger on or off

You can also edit, disable, or delete individual triggers within a workflow. Hovering over a trigger will show edit and delete options. To disable the whole trigger, toggle it off. Turning it off leaves the workflow and its history in place, so you can turn it back on later without rebuilding anything.

Runs

Every time a workflow starts, whether from a trigger or from Run, it records a run. Recent runs lists them newest first, and you can filter to Completed, Failed, or Stopped.

Each row names the workflow, says what started it, counts the steps, and shows how long ago it happened alongside its status.

Expanding a run opens what happened inside it: a run ID you can copy, the list of steps with a status mark and a duration on each, and the final result the workflow returned. Expanding a single step shows what that step produced, which is where you look when a run finished but the result wasn’t what you expected.

What Workflows Cost

Workflows draw on the same credits as the rest of GlideOS. What a workflow costs comes down to a mix of factors including how many steps there are, which integrations (if any) are used, and what actions occur within the workflow.

Credits per step

Steps are charged in brackets. The first 100 steps in a run cost 0.1 credits each. The next 900 cost 0.05 each. Steps beyond that cost less again.

A longer run doesn’t move all of its steps to the cheaper rate. Only the steps past each cutoff get it.

A 500-step run costs 30 credits: 10 for the first 100 steps, plus 20 for the next 400 steps.

A 2,500-step run costs 85 credits: 10 for the first 100 steps, plus 45 for the next 900 steps, plus 30 for the last 1,500 steps.

Seeing the cost before you commit

Each trigger on a workflow shows an estimated monthly credit figure, worked out from that workflow’s recent runs. The estimate counts steps plus any AI and integration usage, and GlideOS labels it as an estimate because actual costs vary with what each run does.

Workflow steps are entirely dependent on the data that they’re working with, which will often change with each run, making the cost unpredictable. We recommend monitoring your estimated and actual workflow runs closely and reducing the amount of data you’re working with or the frequency with which the workflow runs to ensure you’re keeping costs down.

Where workflow usage shows up

Workflow credits fold into your organization’s credit total. To find them, click your organization name at the top of the left sidebar. Click Settings and then select Usage. The Workflows breakdown under the Credits tab lists steps, step credits, AI, and integration usage for each workflow.