Connect CalendarLink to Xitoring

Both apps 25CalendarLink 9Xitoring 16

• Trigger
  New Upcoming Event

  Triggered when a new upcoming event is added to your CalendarLink organisation.

• Action
  Create New Event

  Creates an event in a CalendarLink collection and returns its add-to-calendar link. Times use the format 2026-09-01 09:00:00. Optionally turns on RSVP with a deadline, attendee limit and notification settings.

• Action
  Find Event

  Searches your CalendarLink events for one whose title contains the text you give, and returns the first match with its add-to-calendar link, times and RSVP counts.

• Action
  List Contacts

  Returns a page of the contacts in your CalendarLink organisation, 15 per page, along with how many pages there are.

• Action
  List Event Collections

  Returns every event collection in your CalendarLink organisation, with each collection's ID, name, description, public link and event count.

• Action
  List Event Registrations

  Returns a page of the people who signed up for one CalendarLink event, 15 per page. The event must have RSVP turned on.

• Action
  List Past Events

  Returns a page of your CalendarLink events that have already finished, 15 per page, newest first.

• Action
  List Upcoming Events

  Returns a page of your CalendarLink events that have not happened yet, 15 per page.

• Action
  Update Event Collection

  Changes the settings of one CalendarLink event collection — its name, description, appearance, what visitors can add and whether sign-up is required. Only the fields you fill in are changed; the rest keep their current values.

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