Connect Pipefy and Sorry

Both apps 34Pipefy 17Sorry 17

• Trigger
  Done Card

  Triggers when a card is done.

• Trigger
  Moved Card

  Triggers when a card is moved.

• Trigger
  New Card

  Triggers when a new card is created.

• Trigger
  New Database Record

  Triggers when a new record is created.

• Trigger
  Updated Card Field

  Triggers when a card field is updated.

• Trigger
  Updated Record Field

  Triggers when a record field is updated.

• Action
  Create Card

  Creates a card in a Pipefy pipe, filling in its start form fields.

• Action
  Create Record

  Creates a new table record.

• Action
  Delete Card

  Permanently deletes a card from its pipe.

• Action
  Delete Database Record

  Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.

• Action
  Find Card

  Returns the cards in a pipe whose chosen field matches the specified value.

• Action
  Find Database Records

  Find a database records by title.

• Action
  Get Card

  Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.

• Action
  Get Database Record

  Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.

• Action
  Move Card

  Moves a Pipefy card to another phase of its pipe.

• Action
  Update Card Field

  Sets a new value on one field of an existing Pipefy card.

• Action
  Update Database Record

  Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.

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