A lot of requests for an automation start in Slack. "Can someone post the new deals here every Monday?" "Which HubSpot deals closed this week?" Then someone has to open another app, find the right screen and build it, and the request waits until they get around to it.
Now you can ask Lodol directly. Mention @Lodol in a channel and it answers in a thread, or write to it in a direct message. It looks things up for you on the spot, and it turns the jobs you describe into workflows you see before anything runs.
Ask a question, get the answer
A question that only reads is answered right there in the thread, without building anything. "@Lodol which HubSpot deals closed this week?" comes back as a short list. "@Lodol what's our refund policy? It's in a doc in Drive somewhere" has Lodol find the document in your Google Drive, read it and link it in its reply. Nothing is saved or changed.
Hand over a job, get a workflow
Anything that sends or changes something becomes a workflow. Say "@Lodol every Monday at 9, post last week's new HubSpot deals here". Lodol builds it and replies with a card:
- Its name, which opens the workflow in Lodol.
- What starts it, such as "Every Monday at 09:00", and whether it's on.
- A picture of its steps, drawn the way the editor draws them.
- What it still needs, such as "Before it can run: connect Google Sheets, then fill in 1 setting in Lodol."
- One button: Run, Turn on, or Finish setup in Lodol.
Where a detail is missing, Lodol picks a sensible default and says what it chose. What only you can pick, such as which spreadsheet or which channel, it leaves for you to fill in rather than guessing.
You see it before it runs
Nothing starts until someone presses the card's button. Even "build it and run it now" waits for you to look at the card first. That matters, because Lodol in Slack can get things wrong, like anything that works from a sentence. The card is where you catch it.
- A scheduled workflow, like the Monday post, waits to be turned on. Once it is, it runs by itself from then on.
- A workflow you run once is followed in the thread: Lodol says how the run went, with a link to it, or the error if it failed. If the workflow needs inputs, Run opens a short form for them first.
- A change is one more message in the same thread, such as "@Lodol make it 8:30 instead". It changes that workflow rather than building a second one.
Admins can let people run workflows straight from chat, in Lodol's Settings, under Slack. Until they do, review stays on.
It works as you
The first time you ask, Lodol shows you a Connect Lodol button that only you can see. Press it, allow, and go back to Slack, where it's already working on what you asked. From then on, everything it looks up, builds or runs for you is done with your Lodol account: your role and your workspace's rules. A teammate in the same channel connects their own account, and never acts through yours.
You connect through the same sign-in screen Claude and ChatGPT use when they build workflows in Lodol, and Lodol in Slack builds with the same tools they do. So what it makes is an ordinary Lodol workflow, in the same list as everything else your team built, with every run recorded.
Safe in a shared channel
- It hears only what's meant for it. A message reaches Lodol when someone mentions @Lodol or writes to it directly. Teammates talking to each other are left alone.
- You press Run. Anything that sends or changes something waits for a person, unless your admins decide otherwise.
- It doesn't delete. Ask it to delete a workflow and it points you to Lodol, where you can see what you're removing first.
- It doesn't touch settings or connections. Changing settings and connecting apps happen in Lodol, by a person.
And it can never do more than your own role in Lodol allows.
One Lodol in Slack
It's the same @Lodol app that already delivers Lodol's notifications in Slack, so your workspace has one Lodol there, not two. Getting started takes three steps:
- A Lodol admin, once: in Lodol, open Settings, then Slack, and choose Add to Slack.
- Each person, the first time: press the Connect Lodol button that only you can see.
- Anyone, any time: invite @Lodol to a channel and mention it, or message it directly. Try "@Lodol what workflows do I have?"
What it's good for
The jobs that fit best are the ones your team already asks each other for in Slack:
- A quick lookup. "What's in the onboarding checklist doc?" "Which deals are still open in HubSpot?"
- A regular post. "Every weekday at 9, post 'Standup in 5 minutes' here."
- Something that should happen on its own. "When someone pays us in Stripe, add them to the revenue sheet and thank them by email."
- A workflow you already have. "Show me the invoice reminders workflow", then Run on its card.
For a workflow you'd rather start from than describe, the template library has ready-made ones that post to Slack, such as Weekly HubSpot lead report to Slack and Post important emails to a Slack channel. And for alerts people actually read, see Slack alerts your team won't mute.
What it costs
Lodol for Slack is on every plan, Free included, at no extra cost. A workflow it builds counts runs like any other: once per run, however many steps it takes. See pricing for each plan's runs.
Ask @Lodol for your first automation.
Start free, add Lodol to Slack from Settings, and ask in a sentence. It builds the workflow, and you press Run. See it in action on the Lodol for Slack page.