Connect Caspio and ilert

Both apps 21Caspio 8ilert 13

• Trigger
  Deleted Record

  Fires when a record is deleted from the selected Caspio table. Instant self-registering webhook (table.recordDelete) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New or Updated Record

  Fires when a record is inserted or updated in the selected Caspio table. Instant self-registering webhook registering both table.recordInsert and table.recordUpdate — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Trigger
  New Record

  Fires when a new record is inserted into the selected Caspio table. Instant self-registering webhook (table.recordInsert) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table. Payload: trigger.body = {data:[record...], objectName, eventType, eventDate, eventId, ...}.

• Trigger
  Updated Record

  Fires when a record's field value changes in the selected Caspio table. Instant self-registering webhook (table.recordUpdate) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.

• Action
  Download File from Field

  Download the file stored in an Attachment-type field of a specific record. Returns the raw file content.

• Action
  Find Records

  Query records from a selected Caspio table with an optional WHERE filter, ORDER BY, and limit. Returns the matching records.

• Action
  Find View Records

  Query records from a Caspio View (a saved joined/filtered/aggregated dataset spanning tables). Optional WHERE / ORDER BY / limit.

• Action
  Upload File to Field

  Upload a file (from a URL) into an Attachment-type field of a specific record. Table from a dropdown, the attachment field and record ID (the record's primary-key value) are supplied per call. Requires an Attachment-type column (not the legacy File type).

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