Integration
Connect Particle to Transport for The Netherlands
When something happens in Particle, your agent does the next thing in Transport for The Netherlands. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Particle and Transport for The Netherlands to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Particle and Transport for The Netherlands
Triggers and actions 1 trigger · 12 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
- Execute a logic function
Run a configured Particle Logic function and return its result.
- Get ledger instance
Retrieve the current data for a ledger instance (shared cloud/device key-value state).
- List devices
List all devices in your account or product fleet.
- Publish an event
Publish a custom event to the device cloud so other devices or integrations can subscribe to it.
- Set ledger instance data
Update the data stored in a ledger instance.
Action
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
- Find passtimes by stop area
Get the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
- 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.
- List journeys
List the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
- 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.
- 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.
- 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.
Each app on its own
Reviews