Roll back to what worked
Every edit is a version. Open any one to see what changed, and restore it in a click.
IT & Security
Every report triaged. Every change on the record.
Lodol runs the work around every report, alert and access change, across Slack, Jira, Okta and the tools you already run. The risky steps wait for a person.
Free to start, no credit card. Every plan has unlimited seats.
- Start
SlackWhen someone posts in #report-phishing.
Anthropic2.8sRead it for the usual phishing signs.
- Slack0.4s
Reply in their thread with what to do.
Google Sheets0.6sLog the report and the verdict.
Fits your stack
Keep your tools. Lodol runs what's between them.
No new console for your team to watch. Lodol picks up the report, does the lookups and the paperwork, and hands a person the decision.
Something's reported
A message in the security channel, a mail to the reports inbox, an alert or an incident starts the work.
It gets looked up
Who registered a domain, who runs an address and what a URL scans as, before anyone opens it.
It lands in the queue
A ticket in the tool your responders already work from, with what was found on it.
Access changes
Users suspended, sessions revoked or groups changed in your identity provider, once a person confirms.
People get told
A reply in the reporter's thread, a page to on-call, or one summary email.
1,455 apps and 19,365 actions in all, and a workflow can call any other tool’s API directly, so nothing has to move for Lodol to fit in.
Explore all integrationsReady to run
Start from one that already works.
Built and tested by our team, and written to report rather than conclude. Open one, connect your apps, and it runs.
On new messageTriage reported phishing in Slack
When someone reports a suspicious message in Slack, assesses it for phishing indicators, replies in thread and logs it.
A first pass, not a verdict: it never calls anything definitely safe, and every report is logged so a wrong call can be found.
Open this template
On new emailTurn reported suspicious mail into Jira tickets
Opens a Jira ticket for each message your people report, and adds later reports of the same sender to the ticket already open.
Copied from the message, never scored. One ticket per sender, and a failed run repeats a report rather than losing it.
Open this template
On new emailFlag emails that link to unfamiliar websites
Posts to Slack when new mail links to a site outside your expected list, with how recently that site was registered and who runs it.
Reports and doesn't conclude: no address is ever visited, and only the host part of a link is used.
Open this template
WeeklyCheck your websites' security settings every week
Each Monday, checks the sites you list for the browser protections they should switch on, and emails what is missing and how to fix it.
One ordinary page request per site you list: a passive check of your own sites, not a scanner.
Open this templateDailyWarn before SSL certificates expire
Checks the certificate on every domain in your sheet each morning and emails the ones running out of time to renew.
One email for everything inside your warning window, and nothing at all when every certificate is fine.
Open this templateEvery 15 minutesWatch your websites for downtime
Checks every site listed in a spreadsheet on a schedule and alerts you in Slack or by email when one goes down or recovers.
Alerts on the change, not the state: one message when a site goes down, and one when it's back.
Open this templateIn control
Access changes wait for a person.
Suspending an account, revoking sessions, removing someone from a group: any step can wait for the person who owns it. Every run is on the record.
See exactly what happened
Every run is traced step by step, so when someone asks when an account was suspended, who approved it and why, the answer is on the record.
Decide who can do what
Owner, admin or member, per person, so the workflows that can change access are edited only by the people who should.
A person confirms the disruptive ones
Put an approval step before an account is suspended or access removed. The run waits until someone decides.
ApprovalWaiting
Suspend Dana Kim's account after a suspicious sign-in alert?
Comment (optional)Called Dana: it wasn't her.
Questions IT and security teams ask first
No. Lodol runs the work between the tools you have: it reads a report, looks things up, opens the ticket in Jira, ServiceNow or Freshservice, and changes access in Okta or Microsoft Entra ID when a person confirms. Your service desk, identity provider and security tools stay where they are.
No. The phishing template is written as a first pass, not a verdict: it never calls anything definitely safe, every reply says it is automated, and every report is logged so a wrong call can be found. Anything that changes access can wait for a person.
Yes, in Okta: suspend, deactivate or unsuspend a user, revoke their sessions, and add or remove them from groups. In Microsoft Entra ID it can create, update and delete users and read their groups and roles. Put an approval step in front of anything that removes access.
No. The security header check makes one ordinary page request to each site you list, as a visitor's browser does, and the uptime and certificate checks look only at the sites in your spreadsheet.
Roles decide who can edit, run or only view each workflow. On Pro you can make your own roles, down to the folder, require single sign-on, and stream the audit log and workflow runs to your SIEM.
Free includes 100 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes. Pro adds single sign-on, SCIM and an audit log you can stream.
Start with the phishing reports.
Point the triage workflow at your security channel and see the next report answered in its thread. Free to start, no credit card.
Free plan, no credit card · Credentials encrypted in transit and at rest · Security and trust