Connect Sendinblue to Transport for The Netherlands

Both apps 31Sendinblue 24Transport for The Netherlands 7

• Trigger
  New contact

  Fires when a new contact is created in Brevo, delivered via a Brevo account webhook subscribed to the "contact created" (contactUpdated/contact) event on Accounts and Settings > Webhooks. Concrete delivery mechanism to be classified during implementation.

• Trigger
  Updated contact

  Fires when an existing contact is updated, delivered via a Brevo account webhook subscribed to the contact-updated event. Concrete delivery mechanism to be classified during implementation.

• Action
  Add contact

  Adds a new contact

• Action
  Add contact attribute

  Creates a new contact attribute in Brevo (Sendinblue) under the chosen category and name.

• Action
  Add contact to list

  Adds existing Brevo contacts to a contact list, identified by email address, external ID or contact ID.

• Action
  Add email campaign

  Create an email marketing campaign.

• Action
  Add event

  Records a custom event against a Brevo contact, optionally updating contact attributes and attaching event properties.

• Action
  Add list

  Creates a new, empty contact list inside a Brevo folder.

• Action
  Add sender

  Creates a new email sender in Brevo. Brevo sends a verification email to the sender address; the sender must be verified before it can be used in campaigns.

• Action
  Delete contact

  Delete a contact.

• Action
  Delete email campaign

  Deletes an email campaign that has not been scheduled.

• Action
  Delete list

  Delete a contact list.

• Action
  Get contact

  Fetches a contact by email, ID, SMS number or external ID. An error occurs if the contact is not found.

• Action
  Get email campaign

  Get an email campaign's report/details by id.

• Action
  Get list

  Retrieve the details of a Brevo contact list by its ID, including name, folder, subscriber counts and campaign statistics.

• Action
  List contact attributes

  Lists all contact attributes defined in the Brevo account, grouped by category.

• Action
  List contacts

  Returns all contacts in the Brevo account, optionally filtered by dates, contact IDs, list or segment, or an attribute value.

• Action
  List lists

  Lists all contact lists in the Brevo account.

• Action
  List senders

  Lists the email senders in your Brevo account, optionally filtered by domain or dedicated IP.

• Action
  List transactional emails

  Lists transactional emails sent from your Brevo account, filtered by recipient email, template, or message ID. Covers the past 30 days unless a start and end date are given.

• Action
  Send transactional email

  Sends a transactional email to one or more recipients, using inline HTML/text content or a saved Brevo template.

• Action
  Update contact

  Update an existing contact's attributes/lists.

• Action
  Update email campaign

  Update an email campaign.

• Action
  Update list

  Updates an existing Brevo contact list's name and/or moves it to a different folder.

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