Connect Readwise to Transport for The Netherlands

Both apps 20Readwise 13Transport for The Netherlands 7

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

• Action
  Find passtimes by line

  Get the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.

• Action
  Find passtimes by stop area

  Get the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.

• Action
  Find passtimes by timing point

  Get the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.

• Action
  List journeys

  List the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.

• Action
  List lines

  List all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.

• Action
  List stop areas

  List all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.

• Action
  List timing points

  List all timing point codes (bus stops, tram/train stops, and virtual points) known to the OVAPI within its current uptime.

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