Connect Better Stack to Transport for The Netherlands

Both apps 23Better Stack 16Transport for The Netherlands 7

• Trigger
  New Monitor Status Change

  Fires when a monitor's status changes (up/down). Poll GET https://uptime.betterstack.com/api/v2/monitors and detect status transitions, or use vendor status-change webhook if available.

• Trigger
  New or Updated Incident

  Triggers when new incidents are created, or when existing incidents are updated.

• Trigger
  On-Call Contact Changed

  Triggers when an on-call contact changes.

• Action
  Acknowledge Incident

  Acknowledges an incident.

• Action
  Add Heartbeat

  Create a new heartbeat check. POST https://uptime.betterstack.com/api/v2/heartbeats

• Action
  Add Incident Comment

  Adds a comment to an incident.

• Action
  Add Monitor

  Create a new uptime monitor. POST https://uptime.betterstack.com/api/v2/monitors

• Action
  Create Incident

  Creates an incident that notifies the team.

• Action
  Delete Heartbeat

  Remove a heartbeat check by id. DELETE https://uptime.betterstack.com/api/v2/heartbeats/{id}

• Action
  Delete Monitor

  Delete an uptime monitor by id. DELETE https://uptime.betterstack.com/api/v2/monitors/{id}

• Action
  Find Incident

  Finds an Incident.

• Action
  Find On-Call Contact

  Finds On-Call Contact. Supports time lookup.

• Action
  Get Monitor

  Retrieve a single monitor by id. GET https://uptime.betterstack.com/api/v2/monitors/{id}

• Action
  List Monitors

  List all uptime monitors. GET https://uptime.betterstack.com/api/v2/monitors (paginated)

• Action
  Resolve Incident

  Resolves an incident.

• Action
  Update Monitor

  Update an existing monitor's settings. PATCH https://uptime.betterstack.com/api/v2/monitors/{id}

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