Connect Readwise and Sorry

Both apps 30Readwise 13Sorry 17

• Trigger
  Any Document Created (Readwise Reader)

  Triggers when a new Document is created in Reader.

• Trigger
  Document Archived (Readwise Reader)

  Triggers when user archive Reader document.

• Trigger
  Document Finished (Readwise Reader)

  Triggers when user finishes reading the document in Reader (reaches 99% article done).

• Trigger
  Document Moved to Inbox (Readwise Reader)

  Triggers when user moves document to inbox.

• Trigger
  Document Moved to Later (Readwise Reader)

  Triggers when user moves Reader document to later section.

• Trigger
  Document Shortlisted (Readwise Reader)

  Triggers when user shortlists a document in Reader.

• Trigger
  Document Tags Updated (Readwise Reader)

  Triggers when user updates tags in a Reader document.

• Trigger
  Feed Document Created (Readwise Reader)

  Triggers when a new (feed) Document is created in Reader.

• Trigger
  Highlight Created (Readwise)

  Triggers when a new highlight has been created in Readwise.

• Trigger
  Highlight Tag Created (Readwise)

  Triggers when user added a tag to a highlight.

• Trigger
  Non Feed Document Created (Readwise Reader)

  Triggers when a new (non feed) Document is created in Reader.

• Action
  Add Document (Readwise Reader)

  Add Document to Reader

• Action
  Create Highlight (Readwise)

  Create a new highlight in Readwise.

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