All integrationsMonitoring
FireHydrant
Declare and run incidents, post updates, track tasks and milestones, and record changes in FireHydrant.
- actions
- 25
- triggers
- 10
Triggers
Start a workflow when something happens in FireHydrant.
- New incidentRuns when an incident is declared in FireHydrant.
- Incident resolvedRuns when a FireHydrant incident is resolved.
- Incident closedRuns when a FireHydrant incident is closed.
- Incident milestone changedRuns when a FireHydrant incident moves to another milestone, such as Mitigated or Resolved.
- Incident severity changedRuns when a FireHydrant incident is given a severity or its severity changes.
- Incident priority changedRuns when a FireHydrant incident is given a priority or its priority changes.
- New change eventRuns when a change, such as a deploy, is recorded in FireHydrant.
- New serviceRuns when a service is added to FireHydrant's service catalog.
- Runbook startedRuns when a runbook starts running in FireHydrant.
- Runbook run status changedRuns when a FireHydrant runbook run changes status, such as to completed.
Actions
Steps a workflow can run in FireHydrant.
- Create incidentDeclare an incident in FireHydrant. Runbooks whose rules match it start on their own.
- List incidentsList incidents, with filters for text, milestone, severity, priority, tags, services, teams and dates.
- Get incidentGet an incident with its milestone, severity, roles, impacts and link.
- Update incidentChange an incident's name, summary, severity, priority, type or tags. Anything left empty stays as it is.
- Add incident notePost a note to an incident's timeline, and to its status pages if you choose.
- List incident milestonesList the milestones an incident has reached, with when each happened and how long it lasted.
- Set incident milestoneRecord when an incident reached a milestone, such as when it was mitigated. Milestones must stay in their configured order.
- Resolve incidentResolve an active incident.
- Close incidentClose an incident, ending its retrospective phase.
- Archive incidentArchive an incident, which hides it from lists and metrics.
- List incident timelineList the entries on an incident's timeline, such as notes, milestone changes and role assignments.
- Create incident taskAdd a task to an incident.
- List incident tasksList an incident's tasks with their state and assignee.
- Update incident taskChange an incident task's title, state, assignee or due time. Anything left empty stays as it is.
- Add incident linkAttach a link, such as a dashboard or ticket, to an incident.
- Assign incident roleGive a person a role on an incident, such as Commander. FireHydrant tells them.
- Assign incident teamAssign a team to an incident. FireHydrant may page the team's on-call responders.
- Run runbookAttach a runbook to an incident and start its steps.
- List runbooksList your runbooks.
- Create change eventRecord a change, such as a deploy or a configuration change, so responders can link it to incidents.
- List change eventsList recorded changes, with filters for text, services, environments and time.
- Delete change eventDelete a recorded change.
- List servicesList the services in your catalog.
- List teamsList your teams.
- List usersList the people in your organization.
No actions match that.
Automate FireHydrant with Lodol.
Connect FireHydrant, then hand Lodol the job in Slack, Claude or ChatGPT.
We’re letting people in a few at a time.