Event-based Automations
Any signal can start the run.
Automations start from findings, supply-chain events, and other triggers. Ethira acts with full context on assets, owners, and reach.
Trusted by
Triggers
From graph, supply chain, and outside signals.
Lucas de Araújo
Co-founder & CTO
We designed the automation layer around a simple observation: governance work rarely starts on a schedule. It starts when something changes: a finding appears, a vendor has an incident, a contract is signed, a new agent shows up in the estate.
So we made every one of those a first-class trigger. A Custom Finding on the Asset Intelligence graph, a supply chain event, or a webhook from an external system can all start the same run, and the run begins with full context on assets, owners, and reach already attached.
I think of it as closing the loop between knowing and doing. Detection without action is just anxiety; the automation layer is how the graph turns into work.
Custom Findings
Rules query the Asset Intelligence graph. When a finding is produced, it becomes an event that starts an automation.
Supply chain events
Vendor incidents, posture changes, and other supply chain signals trigger the right playbook without a manual handoff.
External triggers
Webhooks, Slack, and third-party platforms can start automations too, still with full graph context attached.
Runs
Runs that carry their context
Rafael Correia
Founding Engineer
I implemented the run engine behind these automations. The principle I held onto is that a run should never start from a spreadsheet export. It reads the same live graph the rest of Ethira sees, so owners, evidence, and diligence steps are attached from the first second.
When a run finishes, the result lands where the team already works: a Slack message, a ticket, a review request, with the evidence bundle attached. No one has to reconstruct why the automation fired or what it saw.
That is how we keep automations trustworthy enough to leave on. Every step is inspectable, and every outcome traces back to the graph state that caused it.
Get started
Close the loop from signal to action.
Connect Asset Intelligence, Custom Findings, supply chain signals, and external triggers, and let automations run when events fire.