Getting started
Introduction to VisualAutomate
Build automations and AI workflows on a drag-and-drop canvas, connect the services you already use, and watch every run live.
VisualAutomate is a workflow automation platform. You build an automation by dragging steps onto a canvas and drawing lines between them. Each step is a small module that does one thing (send a mail, ask a model, trim a video, call an API) and the lines between them decide what runs, in what order and under which conditions.
When a workflow runs, it runs on our infrastructure, in a secure environment. You watch it step by step, with the input, output and logs of every step, while it happens.
From a blank canvas to a workflow that runs, in a few minutes.
Core conceptsWorkflows, steps, lines, runs and credits: the words used everywhere else.
How it works
Three things, and between signing up and having something that runs, this is the whole job. No servers to pick, no deployment, nothing to install.
Connect an account
Sign in to the services the workflow should act as: your mailbox, your CRM, your spreadsheet. The authorisation happens on their side, and what comes back is stored encrypted in a vault. It is never shown back to you and never reaches the browser. Hundreds of apps, or any API over plain HTTP.
Draw the steps
Drag steps onto a canvas and join them. Put conditions on a line so a path is only taken when the data says so, and give a step a second route for when it fails. Loop over a list and the steps after it run once per item. A saved canvas is the live one.
Choose what starts it, then watch it
A run writes a log as it goes, step by step, with what went in and what came out. A step that fails is retried on its own, and you can run a run again on the same data once you have fixed what went wrong.
Four ways a workflow starts
Most of the value of an automation is that nobody is present when it runs. So it is worth being plain about what makes one go.
For the workflows you supervise, and for every one while you are still building it.
On a scheduleEvery hour, every weekday at nine, once on a date. Exactly one run per due schedule.
From a webhookAnything that can send an HTTP request can start a run, with its payload as input.
When mail arrivesNew mail in a connected mailbox becomes a run, with the message and attachments in hand.
What you can build
Every example below is made of steps that exist today.
- Sales and CRM. A new lead in the CRM before anybody opens the email: a webhook, an AI step that extracts the fields, a contact lookup, a new deal and a message to the team.
- Support. Every ticket sorted before a person opens it: an AI step that classifies it, and a route per category.
- Finance. Yesterday's payments in a spreadsheet every morning, on a schedule.
- Media. One recording turned into a week of clips: probe, trim, reframe and subtitle with the video steps, then transcribe with Whisper.
- Operations. Onboarding a new colleague without a checklist nobody follows.
- Engineering. An alert becomes an issue with the context attached, or two systems that will not talk to each other are glued together over HTTP.
Free to start
The free plan has five workflows and a hundred runs a month, with no card and no time limit. Enough to build something real and find out whether it works. See Credits and billing.
Where to go next
Was this page helpful?