Processes (Workflows)

Who is this for? Anyone who builds or runs automations in Adomo. A process (you may also hear "workflow") is a standard operating procedure that Adomo executes step by step on your behalf.

The Processes section of the sidebar is where your automations live: everything your team has built, each one's run history, its schedule, and its current status.

Create a process

There are four ways to create one. All of them produce a draft that you review and approve before anything goes live.

Describe it in chat. The most common path. Tell Adomo how the work gets done today ("when a new deal closes, create the onboarding checklist, notify the CS team, and schedule a kickoff call") and it drafts the process for you.
Start from a template. Browse the template catalog for common SOPs and adapt one.
Generate from a knowledge document. If your SOP already exists as a document in Knowledge, Adomo can turn it into a runnable process directly.
Import. Bring in a process definition exported from another workspace (you can export one from its process page).

Review and approve the draft

Every draft shows you, before you approve it:

The steps, in order, with what each one does
Which integrations and tools it will use
Where it pauses for a human decision
Any schedule or trigger it will run on

You can refine the draft by telling Adomo what to change in chat, or by editing it directly in the draft panel. When it looks right, click Approve & Activate (in chat) or Approve process (in the draft panel). Approval creates an immutable version: every run records exactly which version it executed, so you can always answer "what did this process do at the time?"

Nothing runs without an approved version. AI drafts; humans approve.

What a process can do

Steps in a process can:

Act in your connected systems - read and write records in your CRM, ERP, accounting, files, calendar, and anything else your admin has connected (see Integrations).
Reason with AI - summarize, draft, classify, extract, compare, with web search when needed.
Branch and wait - if/else conditions, multi-way switches, and timed waits ("pause until Friday 9am").
Pause for people - decision steps that route an approval to the right person, and request steps that collect input from someone (see Approvals and Decisions).
Notify - send one-way messages through Email, SMS, Slack, Microsoft Teams, Google Chat, WhatsApp, mobile push, or in-app. Decision and request steps (the steps that wait on a person) can send automatic reminders if no one responds.
Compose - call other processes as sub-steps, or wait for another process to finish.
Generate media - create images and short videos with AI, and build slide decks (PPTX or PDF) from your content.

Steps that reason with AI or generate media consume your workspace's monthly credit allowance. Admins can see usage under Settings > Billing - see the Billing article.

Ways to run a process

Manually - click Run now on the process page, or ask in chat.
On a schedule - recurring, timezone-aware schedules (daily, weekly, monthly, or custom). The schedule shows in plain English on the process page.
From an external system - each process can expose a secure webhook URL so your other systems can trigger it.

Test runs

Before relying on a process, run it in test mode. Each step has a Live/Mock toggle: mocked steps return fixture data (a default mock output, or custom JSON you provide) instead of executing, so nothing is sent to your external systems for those steps. Steps default to Mock; any step you switch to Live executes for real. Keep steps that write to external systems mocked to validate logic safely.

Watch a run

Every run, live or historical, shows a step-by-step timeline:

Each step's status, timing, inputs, and outputs
Any decisions requested, who responded, and what they chose
Clear error detail when a step fails

If you ever wonder "what did the AI do here?", the run timeline is the answer. Nothing runs silently.

Sharing and permissions

Processes are shared like documents. Each one can be shared with individual people, groups, or the whole workspace at three levels:

View - see the process and its runs
Contribute - run it
Manage - edit, share, pause, or archive it

FAQ

How do I pause or retire a process?

On the process page, use Pause schedule (available on scheduled processes; the schedule stops and you can resume any time, though webhook triggers and manual runs still work while paused) or Archive process (retired; it can no longer be run, history retained).

What happens if an integration it uses breaks?

The failing step is marked with a clear error in the run timeline and the run is marked failed; it does not fail silently. Adomo also checks that required integrations are connected before a draft can be approved, so most connection problems are caught up front. If a connection breaks later, fix it under Integrations and run the process again.

I started a run by mistake. How do I stop it?

Open the run and click Cancel in its header. Pausing or archiving the process stops future runs, but it does not stop a run that is already in flight.

Why does my run look stuck?

Open the run's timeline - the waiting step shows what it needs. The usual reasons: it is waiting on a human decision (check the Approvals page, or nudge the assigned approver), or a timed wait step has not elapsed yet. If a step failed instead, the timeline shows the error.

Can I change a process that's already live?

Yes. Edit it (in chat or the draft panel), which creates a new draft; approving the draft creates the next version. Runs already in flight finish on the version they started with.

Who pays attention to all these runs?

You don't have to watch them. Anything that needs a human routes a notification through each person's preferred channels (see Notifications (for Users)), and the Home page summarizes what's running, what's waiting on you, and what recently finished.