Connect Samply and Sorry

Both apps 34Samply 17Sorry 17

• Trigger
  New player

  Webhook event player.created.

• Trigger
  New project

  Webhook event project.created.

• Trigger
  Player updated

  Webhook event player.updated.

• Trigger
  Project updated

  Webhook event project.updated.

• Action
  Add comment

  /projects/:projectid/files/:fileid/comments. Body: message, parentid, completed, pinned, audioTimestamp, audioTimestampEnd. fileid must be a version, not a stack.

• Action
  Add file

  /projects/:projectid/files with name, mimeType, size, optional parentid; returns boxid and signed upload url, then PUT file bytes to url.

• Action
  Create Folder

  Creates a new folder in an existing Samply project

• Action
  Create Player

  Creates a new player in Samply

• Action
  Create Project

  Creates a project in Samply

• Action
  Get File

  Returns a box object (file, folder or stack) by id within a project.

• Action
  Get Player

  Returns one player (link) by id.

• Action
  Get Project

  Retrieves a project from Samply

• Action
  List comments

  /projects/:projectid/files/:fileid/comments. Returns array of comment objects for a file.

• Action
  List Files

  returns an array of all box objects (files, folders, stacks) in a project; a file box (object: "file") id supplies the file_id Add comment needs. Read-only.

• Action
  List Projects

  returns an array of all projects the caller owns (id, name, files). Read-only; supplies a project_id for downstream ops.

• Action
  Update Player

  Updates an existing player in your Samply library

• Action
  Update Project

  Updates an existing project in your Samply account

• Trigger
  New notice

  Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

• Action
  Add component

  Creates a new component on a Sorry status page, optionally nested under a parent component.

• Action
  Add notice

  Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

• Action
  Add notice update

  Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

• Action
  Add subscriber

  Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

• Action
  Delete notice

  Deletes a notice (incident, maintenance or general) from a Sorry status page.

• Action
  Delete subscriber

  Permanently removes a subscriber from a status page.

• Action
  Get notice

  Returns a single notice from a status page, including its type, state, subject, synopsis and link.

• Action
  Get status page

  Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

• Action
  List components

  Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

• Action
  List notices

  Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

• Action
  List notice updates

  Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

• Action
  List status pages

  Returns all status pages in your Sorry account, optionally filtered by name or creation date.

• Action
  List subscribers

  Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

• Action
  Update component

  Updates a component on a Sorry status page, such as its name, description, position or parent component.

• Action
  Update notice

  Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

• Action
  Update status page

  Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

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