Connect Rootly to Qdrant

Both apps 33Rootly 18Qdrant 15

• Trigger
  New Alert

  Triggers when a new alert is created in Rootly.

• Trigger
  New Incident

  Triggers when a new incident is created in Rootly.

• Trigger
  New Pulse

  Triggers when a new pulse, such as a deploy or config change, is recorded in Rootly.

• Action
  Add action item

  Adds an action item (task or follow-up) to a Rootly incident.

• Action
  Add service

  Creates a new service in Rootly's service catalog.

• Action
  Create Alert

  Creates a new alert in Rootly and returns its ID and status.

• Action
  Create Incident

  Creates a new incident in Rootly and returns its ID, status and link.

• Action
  Create Pulse

  Records a pulse in Rootly, such as a deploy or configuration change, and returns its ID.

• Action
  Get Alert

  Returns one Rootly alert by its ID.

• Action
  Get Incident

  Returns one Rootly incident by its ID.

• Action
  Get Pulse

  Returns one Rootly pulse by its ID.

• Action
  List alerts

  Returns alerts in your Rootly organization, optionally filtered by status, source, service, team, environment, label or time range.

• Action
  List incidents

  Returns incidents in your Rootly organization, optionally filtered by status, severity, services, teams, dates and more.

• Action
  List pulses

  Returns the pulses (deploys and other change events) recorded in Rootly, optionally filtered by source, service, environment, label, ref or time range.

• Action
  List services

  Returns the services in your Rootly organization, optionally filtered by name, slug, external ids or creation date.

• Action
  List teams

  Returns the teams in your Rootly organization, optionally filtered by name, slug, color, external ids or creation date.

• Action
  List users

  Returns the users in your Rootly organization, optionally filtered by search text, email, role or creation date.

• Action
  Update incident

  Updates an existing Rootly incident's title, status, severity, teams, services, timestamps and other details.

• Action
  Add collection

  Creates a new Qdrant collection with the given name and vector configuration.

• Action
  Add payload index

  Creates a payload index on a field of a Qdrant collection so that filters on that field run fast.

• Action
  Add points

  Adds points (vectors with optional payloads) to a Qdrant collection, overwriting any existing point with the same id.

• Action
  Add snapshot

  Creates a new snapshot of a Qdrant collection and returns the snapshot's name, size and checksum.

• Action
  Count points

  Returns the number of points in a Qdrant collection, optionally only those matching a payload filter.

• Action
  Delete collection

  Deletes a Qdrant collection and all of the points and data stored in it.

• Action
  Delete points

  Deletes points from a Qdrant collection, either by a list of point ids or by every point matching a filter.

• Action
  Find points by vector

  Returns the points in a collection whose vectors are closest to the vector you supply, ranked by similarity score, with their payloads.

• Action
  Get collection

  Returns the details of a Qdrant collection: its status, point and vector counts, segment count, configuration and payload index schema.

• Action
  Get point

  Returns a single point from a Qdrant collection, including its payload and vector.

• Action
  List collections

  Returns the names of all collections in your Qdrant cluster.

• Action
  List points

  Returns the points stored in a Qdrant collection, optionally narrowed by a payload filter and ordered by a payload field.

• Action
  List snapshots

  Returns every snapshot stored for a Qdrant collection, with each snapshot's file name, creation time, size and checksum.

• Action
  Update collection

  Updates the settings of an existing Qdrant collection, such as its vector, index, optimizer, quantization, strict-mode or metadata parameters.

• Action
  Update point payload

  Sets payload values on points in a Qdrant collection, chosen by point ids or a filter. Keys you supply are added or overwritten; other existing payload keys are kept.

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