Connect iLert to your AI agent

Developer Tools 8 actions available

iLert is an incident response platform for managing alerts, on-call schedules, escalations, incidents, and status pages.

We set up the connection using your own iLert account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

Book a setup call → See pricing
Actions

What your agent can do in iLert

Each one is a real action the agent can take on its own, the same things a person clicking around iLert could do. Read-only by default; write actions are confirmed against your policy.

  • Get Alert Get one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.
  • Get Current User Return the authenticated iLert user, including identity, role, timezone, and active team context. Use this to verify who the API key represents before incident-response work.
  • Get Incident Get one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.
  • List Alerts List iLert alerts with optional state, source, escalation-policy, responder, and report-time filters. Returns one page and a continuation cursor.
  • List Incidents List iLert status incidents with optional lifecycle-state, affected-service, and report-time filters. Returns one page and a continuation cursor.
  • List On Calls Find who is on call for selected escalation policies, schedules, users, and a time window of at most three months. Returns one page and a continuation cursor.
  • List Resources List one incident-response resource catalog: services, teams, escalation policies, or maintenance windows. Use returned IDs as filters or references in alert, incident, and on-call tools.
  • List Schedules List iLert on-call schedules, optionally expanding current or next shifts and schedule definitions. Returns one page and a continuation cursor.
Setup

How we connect it

  1. 1

    Connect your account

    You create a key in iLert, a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

FAQ

iLert questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions iLert's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put iLert to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

Book a setup call → Browse all connections

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by iLert.