Connect Sender to Transport for The Netherlands

Both apps 21Sender 14Transport for The Netherlands 7

• Trigger
  New Group

  Triggers when a new group is created.

• Trigger
  New Subscriber

  Triggers when a new subscriber is added.

• Trigger
  New Unsubscriber From Group

  Triggers when a subscriber is removed from a group.

• Trigger
  Updated Subscriber

  Triggers when a subscriber is updated.

• Action
  Add group

  Create a new subscriber group. Endpoint: POST /v2/groups

• Action
  Add Subscriber to Group

  Adds a subscriber to a group.

• Action
  Add / Update Subscriber

  Adds a new subscriber. If subscriber with the same email exists, updates the subscriber's data.

• Action
  Create Campaign

  Creates a draft campaign

• Action
  Get campaign

  Retrieve details of a single campaign by campaign id. Endpoint: GET /v2/campaigns/{campaign_id}

• Action
  Get subscriber

  Retrieve a single subscriber's data by email or subscriber id. Endpoint: GET /v2/subscribers/{subscriber_id}

• Action
  List groups

  List all subscriber groups on the account. Endpoint: GET /v2/groups

• Action
  List subscribers

  List all subscribers on the account, paginated. Endpoint: GET /v2/subscribers

• Action
  Remove Subscriber From Group

  Removes a subscriber from a group.

• Action
  Unsubscribe Email

  Unsubscribes an email address.

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