Connect Readwise to PhishStats

Both apps 15Readwise 13PhishStats 2

• 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 phishing record

  Polling trigger for newly added phishing URLs. GET https://api.phishstats.info/api/phishing?_sort=-date&_p=1&_size=100 (optionally filtered by _where=(countrycode|tld|asn,eq,value) etc.) — the database refreshes every ~90 minutes; poll no more often than that. Dedup/order by the id or date field (descending). Auth via X-API-Key header (psk_...) or ?apikey=psk_...; anonymous allowed at a lower quota.

• Action
  Find phishing records

  Search the PhishStats phishing database. GET https://api.phishstats.info/api/phishing with _where=(field,operator,value) filters (eq/ne/gt/lt/like, combined with ~and/~or) over fields like url, ip, asn, countrycode, tld, title, score, date, id; _sort=field (-field for desc); _p=page (default 1), _size=records per page (default 20, max 100). Auth via X-API-Key header (psk_...), Authorization: Bearer psk_..., or ?apikey=psk_... query param; anonymous is allowed at a lower quota.

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