What is Lodol?
Lodol runs your automations for you. Say what should happen and when, and Lodol does it every time, with your keys kept safe and every run on the record.
A Lodol workflow is a short list of steps that runs on its own. It starts when something happens in one of your apps, on a schedule, or when you start it, and then works through its steps the same way every time. There is no server to keep running, no script to maintain and no keys sitting in a file.
Log Stripe payments
- Trigger
New Stripe payment
Stripe
Append row
Google Sheets · Revenue sheet
Send a message to a channel
Slack · #sales
This one workflow replaces a script, a cron job, a server and an alert. It starts itself when a payment comes in, uses your Stripe, Google and Slack connections without ever showing their keys, records every run step by step, and emails you if a run fails. The rest of these docs build on this example.
Three ways to build a workflow
Ask your AI tool
Connect Claude, ChatGPT, Cursor or another AI tool and describe what you want. It builds the workflow in Lodol for you.
Start from a template
Pick one of the prebuilt workflows for sales, finance, support and more, then connect your apps.
Build it yourself
Add a trigger and steps in the visual editor, one at a time. The concepts below explain each part.
You can also start workflows and read their results from your own code with the developer API.
The parts of a workflow
| Part | What it is |
|---|---|
| Trigger | What starts the workflow: an event in an app, a schedule, or you. |
| Steps | What it does, in order: app actions such as Append row, and built-in steps such as If or Request approval. |
| Data | What each step produces, which later steps read with @ references such as @payment.amount. |
| Inputs and outputs | Values a workflow can be given when it starts, and values it hands back. |
| Runs | Each time the workflow runs, recorded step by step. |
| Connections and secrets | Your app accounts and API keys, kept encrypted and used by name. |