Connect EasyPost and ilert

Both apps 25EasyPost 12ilert 13

• Trigger
  New tracker update

  Triggers when EasyPost reports a tracker was created or updated, such as a new scan or status change on a package.

• Action
  Add address

  Creates an address (a person, place or organization) in EasyPost, optionally verifying it for deliverability. Returns the saved address with any verification results.

• Action
  Add batch

  Creates a batch of shipments in EasyPost, so they can be bought, labelled, manifested or picked up together. A batch can also be created empty and shipments added later.

• Action
  Add pickup

  Creates a pickup request for a purchased shipment and returns the available pickup rates, which must then be bought to schedule the pickup.

• Action
  Add refund

  Requests refunds for one or more purchased shipping labels by carrier and tracking code, and returns the resulting refund records.

• Action
  Add shipment

  Creates a shipment from a destination address, an origin address and a parcel, and returns the shipment with its available shipping rates.

• Action
  Add tracker

  Creates a tracker for a package tracking code (for labels bought outside EasyPost) and returns its current tracking status and history.

• Action
  Buy shipment

  Purchases a shipping label for an existing shipment using the selected rate, returning the tracking code and postage label.

• Action
  Get address

  Returns an address saved in EasyPost by its ID, including its verification results.

• Action
  Get batch

  Returns a batch of shipments, including its state, shipment statuses, consolidated label and scan form.

• Action
  Get pickup

  Returns a scheduled carrier pickup, including its status, confirmation number, address and available pickup rates.

• Action
  Get shipment

  Returns a shipment, including its addresses, parcel, rates, label and tracking details.

• 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.

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