Connect Apollo to Transport for The Netherlands

Both apps 21Apollo 14Transport for The Netherlands 7

• Trigger
  Account Updated

  Polls Apollo accounts/search for new or updated accounts (dedup on MD5 of the record; accounts/search returns no updated_at). Apollo has no record-change webhook API, so this is a polling trigger.

• Trigger
  Contact Updated

  Polls Apollo contacts/search for new or updated contacts (dedup on MD5 of the record). Apollo has no record-change webhook API, so this is a polling trigger.

• Trigger
  New Account

  Polls Apollo accounts/search for newly created accounts (dedup on account id). Apollo has no record-change webhook API, so this is a polling trigger.

• Trigger
  New Contact

  Polls Apollo contacts/search for newly created contacts (dedup on contact id). Apollo has no record-change webhook API, so this is a polling trigger.

• Action
  Create Account

  An Account is a company that your team has added to Apollo.

• Action
  Create Contact

  A Contact is a person your team has added to Apollo.

• Action
  Create Deal

  Deals are records that you can use to track possible opportunities with your prospective customers.

• Action
  Create Task

  Creates a task for the specified Apollo contact (via /tasks/bulk_create with a single contact).

• Action
  Find Contact

  Find a contact in your Apollo instance by searching for their email. If you have multiple contacts with the same email address, this search returns the contact that was created first.

• Action
  Find Deal

  Returns up to 100 deals (opportunities) that match the specified name. Leave name blank to return all deals.

• Action
  Find Task

  Returns up to 100 tasks for the specified contact. Leave contact_id blank to return all tasks.

• Action
  Update Account

  Update an existing Account.

• Action
  Update Contact

  Update an already existing Contact.

• Action
  Update Deal

  Update an already existing Deal.

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