Automations that live inside your app
Describe what should happen and when. GateBuild builds the workflow into your app itself — no external glue tools, no separate automation bill, no fragile zaps to babysit.
Start buildingBuilt in, not bolted on
A workflow is part of your app's own code and data, created the same way everything else in GateBuild is: by describing it.
Describe it, don't wire it
Say the goal in plain words — "email a receipt when a payment lands, and remind the customer a day before their booking" — and the workflow is assembled for you: trigger, steps, conditions and all. There is no canvas of boxes to connect by hand unless you want to open one up and look.
Triggers from anywhere
Start a workflow from a schedule, a data change (a record created, updated or deleted), a new agent conversation, an incoming connector event, a webhook from another service, or app events like publish, payment and media-ready. If it can happen in or around your app, it can start a workflow.
Waits that survive anything
A wait step can hold for minutes or for days, and it is durable: restarts, deploys and quiet weekends do not lose it. When the time comes — or the condition it was waiting on is met — the workflow picks up exactly where it left off.
Branches on real data
Conditions read your app's live records, not a stale copy: send one email if the order total is over the free-shipping line and another if it is not. Every branch can name a fallback, so a failed step follows the path you chose for failure instead of stopping silently.
Every run, on the record
The Activity view keeps the full run history: what triggered each run, which steps ran, what each step did, and the exact credit cost of the run. When something behaves unexpectedly, the answer is in the history, not in a support ticket.
Debug it in chat
Ask why a run failed and get the failing step, the data it saw and the error it hit — then fix it in words ("skip the email step for free-plan users") and let the next run prove the fix. Workflows can also call your backend functions as steps, so anything your app can compute, a workflow can use.
From sentence to running automation
Four steps, all in conversation.
-
Describe the goal
Tell the builder what should happen, in the words you would use with a colleague. It drafts the workflow and shows you the plan before anything runs.
-
Pick the trigger
Schedule, data change, webhook, payment, publish — choose what starts it, or accept the trigger the builder suggests from your description.
-
Add the steps
Run a backend function, send a designed email, wait, or branch on a condition. Rearrange, add a fallback, or leave it exactly as drafted.
-
Review the run history
Watch the first runs land in Activity with their cost per run. Adjust the workflow in chat whenever your process changes.
Workflows your app will suggest
GateBuild notices the patterns in your app and offers the automations that fit. Four of the most common:
New-user onboarding
When someone signs up, send a welcome email, create their starter records and schedule a follow-up message for day three if they have not finished setting up.
Start with thisNo-show win-back
When a booking passes without a check-in, message the customer with a friendly rebooking link and flag the slot pattern if it keeps happening.
Start with thisRenewal reminders
Seven days before a membership or subscription renews, remind the member what is coming and give them a one-tap way to change or pause it.
Start with thisWeekly check-ins
Every Monday, gather each active user's week in the app and send a short check-in email with their numbers and one suggested next step.
Start with thisNative, not stitched on
The usual way to automate an app is to rent a separate glue tool and stitch it on from outside. Workflows take the other path.
| Separate glue tools | GateBuild workflows | |
|---|---|---|
| Where the logic lives | In a second product, outside your app | Inside the app, next to its data |
| Data access | Whatever an API export happens to expose | Your app's real records, with its own access rules |
| Run history | A separate dashboard, if the plan includes one | In the app's Activity view, beside everything else |
| Cost visibility | A second subscription with its own task limits | Every run shows its credit cost in the history |
| Maintenance | Connections break quietly when either side changes | Changes to the app and its workflows ship together |
Hooks that can say no
Some workflows should not react after the fact — they should stand in front of an action. A blocking hook runs before an action completes: before a record is deleted, before a refund is issued, before a booking is confirmed. It checks the conditions you set and can stop the action, allow it, or route it to a person. Guardrails, written in the same plain words as everything else.
Workflow questions
Which plans include workflows?
Workflows are a Builder-plan feature and up. The gate is labelled here and in the plan comparison, not hidden: Free and Starter apps do not run workflows, and the builder will tell you before you design one that needs a higher plan.
What does one workflow run cost?
About 0.1 integration credits per step. Decision steps are free; wait steps count like any other step. Actions a step performs — sending an email, calling a connector — are charged on top at the same rates they cost anywhere else in your app, and every run's total appears in its Activity entry.
How often can a scheduled workflow run?
At most once every 5 minutes. Schedules tighter than that are almost always a sign the trigger should be an event instead — a data change or a webhook fires the moment it happens, with no polling at all.
I already have automations in another tool. Can I move them?
Yes — describe what the existing automation does, and the builder rebuilds it natively as a workflow: same trigger, same steps, same messages. Most migrations are a short conversation; once the native version is running and its first runs look right in Activity, you can switch the old one off.
What happens if a step fails in the middle of a run?
The run follows the fallback you set for that step — retry, take the other branch, notify you, or stop cleanly. The failure, the data the step saw and the path taken are all recorded in the run history, and you can ask in chat what went wrong.
Can a workflow wait for a person, not just a timer?
Yes. A wait can end on a condition — an approval, a reply, a record changing — as well as on a clock. Combined with a blocking hook, that gives you human-in-the-loop automation: the workflow prepares everything and a person makes the final call.
Put your app on autopilot
Build the app, describe the routine, and let the workflow carry it.
Start building