Summary
Flows are Alta's automation builder — chain a trigger and a sequence of integration actions to move data, send messages, or react to events without writing code. The sidebar item is labeled Workflows (route /workflows), but the feature is referred to externally and in our integration articles as Flows. This article covers the full lifecycle: create, build, publish, toggle on/off, and inspect runs.
Who this is for: Anyone automating Alta with another tool — typically RevOps or anyone who would otherwise reach for Zapier / n8n. You don't need to write code.
Before you start
You'll need permission to create flows in your Alta workspace.
If your flow uses a third-party integration (Salesforce, Klaviyo, Monday.com, Microsoft Teams, etc.), connect that integration first so it shows up in the picker. Each integration has its own dedicated setup article in the Help Center.
Step 1 — Create a flow
In the Alta sidebar, click Workflows.
You'll see two tabs at the top: Workflows (your saved flows) and Runs (every execution).
From the Workflows tab, click New Workflow (to the left of Create with Ask Alta, or in the empty state if you have no flows yet). Alta creates a flow named New workflow and opens it in the editor. You can rename it from there.
To start from a ready-made flow, open the menu on New Workflow and click Templates. When you have no flows yet, Templates is also a button next to New Workflow.
To build the flow in conversation instead, click Create with Ask Alta, the button to the right of New Workflow. A dialog opens. Describe what you want the flow to do and send it. Ask Alta opens in the side panel and starts a chat with your message.
Step 2 — Build the flow in the editor
The editor is a drag-and-drop canvas powered by React Flow. The top bar has the editable flow name on the left and a Draft / Published badge next to it.
Pick a trigger
Every flow starts with one trigger. Click the empty trigger node on the canvas. A few featured triggers appear — for example, a webhook, a scheduled trigger, or an event from Alta. Pick one, or choose All Triggers to open the full list in the right-side panel. That list shows Alta triggers grouped by area, then Utils, then integrations you can open. After you pick a trigger, its settings open in that panel.
Run a Callable Flow
Callable Flow starts a flow when you run it yourself. Publish the flow first, then open the published version and click Run Flow above the trigger. A dialog asks for the data that run starts with.
Sample Data — enter a JSON object. That object is also what later steps see when you test the trigger, and any JSON object is accepted when you run it.
Parameters — give the flow a name and a description, then list the fields a run must receive. Each field has a type (text, number, boolean, date, array, or object) and can be required. The run dialog shows one input per field and will not start a run that does not match.
Later steps read the data you entered under data on the trigger.
Add steps
Click the + below the trigger to add the next step.
Choose what to add. Action opens the full list in the right-side panel. Agent, Ask Alta, Loop on Items, and Router are added immediately. You can also type in the search field and pick a matching action from the results.
In the list, Alta steps are grouped by area, such as People and Campaigns. AI steps are listed under AI. Under Utils and Integrations, open a group and pick a step. Integrations show their categories next to the name. Available actions depend on the integration — for example, Microsoft Outlook Calendar offers Create event, List events, and Delete event; Klaviyo offers Search Profile, Create Profile, etc.
Configure the step in the right-side panel. Each property has its own input — text, dropdown, datetime, etc. — and you can pipe data from earlier steps into any field using the variable picker.
Repeat for as many steps as your flow needs. The canvas is resizable; drag the divider between the canvas and the step panel to give yourself more room.
Step 3 — Publish the flow
A flow only runs when it's Published. The flow editor enforces a strict draft / publish split.
While editing, your changes live in a Draft version. The badge in the top bar reads Draft.
When you're ready, click Publish in the top right. The button stays disabled until the flow has at least one action after the trigger — a trigger alone cannot be published. Hover shows "Add at least one action before publishing". It also stays disabled if a step is incomplete — hover shows "Please fix the errors in the workflow".
Once published, the badge flips to Published and the version becomes the one Alta runs.
Edit a published flow
Published flows are read-only. To change one:
Click Edit in the top right. Alta creates a fresh Draft based on the published version and reloads the editor.
Make your changes.
Click Publish again to make them live, or Discard Draft to throw the draft away and keep the published version unchanged.
Step 4 — Toggle a flow on / off
Back on the Workflows tab, every row has four columns: Name, Integrations (icons for each integration used), Status, and Actions.
The Status column has a switch. Toggle it to set the flow Active or Inactive.
The switch is disabled until the flow has at least one published version. Publish first, then you can toggle.
Toggling Inactive pauses execution — the flow won't run on its trigger until you flip it back to Active.
Step 5 — Monitor runs
Switch to the Runs tab. Every execution of every flow shows up here — success, failure, and in-flight.
From a flow's editor, open the menu to the left of Manage access and click Runs. That opens a Recent runs panel for that flow. Each row shows when the run started, its status, and how long a finished run took. Click a run to show that execution on the canvas, with each step annotated by what happened during that run. View all in the panel opens the Runs tab in a new browser tab, already filtered to that flow.
On a published flow, before you open a run, each step shows a chip with the share of recent production runs of that version that succeeded. Hover the chip to see how many runs reached the step and how many of those succeeded. Steps that none of those runs reached are dimmed. A note at the top of the canvas appears when the flow has more production runs than the summary includes. Opening one run replaces the summary with that run.
On a finished run, open the menu on the row to retry it On latest version. A failed run can also be retried From failed step.
Look through version history
Versions, in that same menu, opens Version history for this flow. Each row is numbered (Version #1, Version #2, and so on), marked Draft or Published, and the version Alta is running is marked Live.
Click an older version to view it on the canvas, with the same production-run summary for that version. Publish is disabled, and Edit and Discard Draft are hidden, so you cannot publish, start another draft, or throw away unpublished edits while the canvas is showing an older version or a run. Click the latest version in the list to return to it.
Step 6 — Export and import a flow
Move a flow between workspaces, or keep a copy, with a JSON file.
Export a flow
From the Workflows tab, open the menu on a flow's row and click Export.
From the editor, open the menu to the left of Manage access and click Export.
Alta downloads a .json file named after the flow. The file contains a version (v1), the flow's name, its trigger, and its steps. Connections are left out, and so are saved sample data and last test dates. Passwords, tokens and secrets typed into a step's authentication fields are removed, and so are headers that carry credentials, such as Authorization or API key headers. Other values you typed into steps, such as URLs and body content, stay in the file, so check them before you share it.
Import a flow
On the Workflows tab, open the menu on New Workflow and click Import. Choose the file, then click Import. Alta creates the flow and opens it in the editor.
After importing, reconnect the integrations. Every step that used a connection or typed credentials is marked as needing attention until you pick a connection or re-enter the credentials. Alta accepts only files exported from Alta Workflows.
Tips and common pitfalls
"Workflows" in the sidebar, "Flows" everywhere else. The product label is Workflows (and the URL is
/workflows), but our integration articles all say "Alta Flows". They refer to the same feature.Drafts vs published — they're separate versions. Editing a flow doesn't change what's running until you hit Publish. Conversely, publishing replaces the live version — there's no preview / staging step.
Discard Draft is destructive and final. It throws away every change you made since the last publish — useful when you want to start a fresh edit from the published baseline.
Status switch stays disabled until first publish. A brand new flow can't be toggled Active. Publish at least once, then toggle.
A trigger alone is not a flow. Publish stays disabled until you add at least one action. Flows that were published earlier with only a trigger are skipped when the trigger fires — Alta does not start a run.
Connect integrations from the relevant integration article first. The step picker shows every integration available in your workspace; if you don't see one you want, install / authenticate it first. Each integration has its own setup article in the Help Center.
Use Runs as your debugger. If a flow misbehaves, open the Runs tab, find the failed run, and step through inputs / outputs. Most failures are typo'd field mappings or expired auth tokens.
Naming matters. Flows accumulate. Give each one a descriptive name from day one — the table column is just text, no descriptions.
