Connect Readwise to Wachete

Both apps 22Readwise 13Wachete 9

• 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
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

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