Connect ilert to Timeero

Both apps 36ilert 13Timeero 23

• Trigger
  New or Updated Incident

  Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

• Action
  Accept Incident

  Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

• Action
  Add Alert

  Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

• Action
  Add maintenance window

  Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

• Action
  Create Incident

  Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

• Action
  Find User on Call

  Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

• Action
  Get alert

  Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

• Action
  Get incident

  Returns a single ilert incident by its id, including its status, severity, affected services and responders.

• Action
  Get maintenance window

  Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

• Action
  List Alert Sources

  Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

• Action
  List incidents

  Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

• Action
  List users

  Returns the users in your ilert account, with their name, email, role and contact settings.

• Action
  Resolve Incident

  Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

• Action
  Add Break

  Adds a break to an active timesheet in Timeero.

• Action
  Add Schedule

  Adds a new schedule for a user or resource, defining date/time and configuration (action, distinct from the existing New Schedule trigger).

• Action
  Add Timesheet

  Creates a new timesheet entry.

• Action
  Add User

  Creates a new user/employee in the company.

• Action
  Approve Timesheets

  Approves one or more Timeero timesheets by their IDs, optionally without notifying the users.

• Action
  Clock in user

  Clocks in a user to start tracking time (action, distinct from the existing Clock In webhook trigger).

• Action
  Clock out user

  Clocks a user out of their open timesheet in Timeero.

• Action
  Create Job

  Creates a new job

• Action
  Create Task

  Create a new task in the system.

• Action
  Delete Job

  Deletes a specific job by its job ID.

• Action
  Delete Task

  Deletes a task in the Timeero company by its ID.

• Action
  Get Group

  Retrieves a specific group's information by group id.

• Action
  Get Job

  Retrieves a single Timeero job by its ID.

• Action
  Get Task

  Retrieves a specific task's information by task id.

• Action
  Get Timesheet

  Retrieves a specific timesheet by id.

• Action
  Get User

  Retrieves a specific user's information by user id.

• Action
  List Jobs

  Returns a list of all jobs within a company.

• Action
  List Users

  Lists the users in your Timeero company, optionally filtered by search text, role, group or active status.

• Action
  Update Job

  Updates a specific job's information.

• Action
  Update Schedule

  Updates an existing schedule's time, assigned user, or other details.

• Action
  Update Task

  Updates a specific task's information.

• Action
  Update Timesheet

  Updates an existing timesheet entry in Timeero.

• Action
  Update User

  Updates an existing user's information.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.