Connect QuintaDB to Xitoring

Both apps 33QuintaDB 17Xitoring 16

• Trigger
  New Database

  Triggers when a new database is created in the connected QuintaDB account.

• Trigger
  New Form

  Triggers when a new form is added to a QuintaDB database.

• Trigger
  New Form Field

  Triggers when a new field is added to a QuintaDB form.

• Trigger
  New or Updated Record

  Triggers when a record in a QuintaDB form is added or changed.

• Trigger
  New Record

  Triggers when a new record is added to a QuintaDB form.

• Trigger
  New Table Record

  Triggers when a new record is added to a QuintaDB form.

• Trigger
  New Table Report

  Triggers when a new report is created on a QuintaDB form.

• Action
  Add form

  Adds a new form (table) to a QuintaDB database. Returns the created form.

• Action
  Create Record

  Adds a new record to a QuintaDB form. The form's own fields are offered for mapping, and the created record's id is returned.

• Action
  Delete form

  Deletes a form (table) and its records from a QuintaDB database.

• Action
  Delete Record

  Deletes a record from a QuintaDB form.

• Action
  Delete records

  Deletes several records from a QuintaDB form in one call.

• Action
  Find Records

  Returns the records in a QuintaDB form that match the conditions you specify.

• Action
  Get record

  Returns one record from a QuintaDB form, including all of its field values.

• Action
  Update Cell

  Changes the value of one field on one QuintaDB record.

• Action
  Update Record

  Changes field values on an existing QuintaDB record. Fields you leave blank keep their current value.

• Action
  Upload file

  Uploads a file into a file field on an existing QuintaDB record.

• Action
  Add check

  Create a new uptime/website/server check. POST /api/v2/check

• Action
  Add group

  Store a new check/server group. POST /api/v2/groups

• Action
  Add heartbeat

  Create a new heartbeat check. POST /api/v2/heartbeat/add

• Action
  Add maintenance schedule

  Create a new maintenance window. POST /api/v2/maintenance-schedules/add

• Action
  Add ticket

  Create a new support ticket. POST /api/v2/tickets

• Action
  Delete check

  Delete a check. DELETE /api/v2/checks/{id}

• Action
  Delete server

  Remove a server from monitoring. DELETE /api/v2/servers/{id}

• Action
  Get check

  Retrieve a single check by id. GET /api/v2/check/{id}

• Action
  Get incident

  Get a single incident's data. GET /api/v2/incidents/{id}

• Action
  Get server

  Retrieve a single server by id. GET /api/v2/servers/{id}

• Action
  List checks

  List all checks. GET /api/v2/check/

• Action
  List groups

  List all groups. GET /api/v2/groups

• Action
  List maintenance schedules

  List maintenance schedules. GET /api/v2/maintenance-schedules

• Action
  List servers

  List all monitored servers. GET /api/v2/servers

• Action
  Resolve incident

  Resolve an open incident. POST /api/v2/incidents/{id}/resolve

• Action
  Update check

  Update an existing check. PUT /api/v2/check/{id}

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