Integration
Connect Chaport to Transport for The Netherlands
When something happens in Chaport, 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 Chaport 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 Chaport and Transport for The Netherlands
Triggers and actions 8 triggers ยท 19 actions
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and โ when asked for โ the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
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.