Integration
Connect FacturaDirecta to Transport for The Netherlands
When something happens in FacturaDirecta, 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 FacturaDirecta 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 FacturaDirecta and Transport for The Netherlands
Triggers and actions 1 trigger · 9 actions
Trigger
New ContactFires instantly when a contact is added in FacturaDirecta. Manual-registration webhook: in FacturaDirecta go to Settings then API and integrations then Webhooks, add a webhook endpoint subscribed specifically to the contact.created event, and paste this triggers minted URL as the endpoint. FacturaDirecta delivers only the events the endpoint is subscribed to, so the payload binds as {{ trigger.body.* }} (contact fields live under data.object, the event kind is in the type field such as contact.created).
Action
Create ClientCreates a client.
Action
Create Sales InvoiceCreates a sales invoice (with line-item support).
Action
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
Action
Find passtimes by stop areaGet the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
Action
Find passtimes by timing pointGet the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.
Action
List journeysList the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
Action
List linesList 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 areasList 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 pointsList 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