Connect Ortto to Xitoring

Both apps 30Ortto 14Xitoring 16

• Trigger
  Fields Updated

  Triggers when the specified field(s) of a record have been updated in your Ortto account.

• Trigger
  New Activity Occurred

  Triggers when a new Ortto activity occurs.

• Trigger
  New Record Created

  Triggers when a new record (contact or organization) has been added to your Ortto account.

• Trigger
  Tag Added/Removed

  Triggers when a tag has beed added to, or removed from, a record.

• Action
  Add Custom Field

  Create a new custom field on the person or organization schema in Ortto. Endpoint: POST /v1/custom-field/create. Vendor doc: https://help.ortto.com/developer/latest/api-reference/custom-field/

• Action
  Create Record

  Create a new record (person, organization), or update an existing record in your Ortto account.

• Action
  Delete Record

  Archive, restore, or permanently delete a person or organization record in Ortto. Endpoint: POST /v1/person/delete (and /v1/organization/delete for accounts). Vendor doc: https://help.ortto.com/a-260-archive-restore-and-delete-people-archive-restore-delete

• Action
  Get Record

  Fetches one or more people, or one or more accounts, by their Ortto ids, returning whichever fields you ask for.

• Action
  List Activities

  Retrieve the activity feed for a given contact in Ortto. Endpoint: POST /v1/person/activities/list (activity log for a contact ID). Vendor doc: https://help.ortto.com/a-773-retrieve-activity-feed-for-a-given-contact

• Action
  Opt Out From SMS

  Opt out a person from all SMS communications.

• Action
  Search or Create Records

  Search your Ortto data for a record based on the provided field or optionally create one if none is found.

• Action
  Tag/Untag Records

  Adds or removes tags on a person or an account in Ortto, matching the record by email address or account name.

• Action
  Unsubscribe a Person

  Unsubscribe a person from all emails.

• Action
  Update Audience Subscription

  Subscribe or unsubscribe a person to/from an Ortto audience. Endpoint: POST /v1/audience/subscribe. Vendor doc: https://help.ortto.com/developer/latest/api-reference/audiences/

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