Integration
Connect Wachete to Transport for Los Angeles, US
When something happens in Wachete, your agent does the next thing in Transport for Los Angeles, US. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Wachete and Transport for Los Angeles, US 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 Wachete and Transport for Los Angeles, US
Triggers and actions 2 triggers · 17 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
- New notification for monitor
Fires when there is a new change notification from the specified Wachete monitor (taskId).
- Create monitor
Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
- Delete monitor
Delete a Wachete monitor by its ID.
- Get monitor
Get information about a specific Wachete monitor by its ID.
- Get monitor data
Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
- List folders
List folder contents, optionally under a parent folder.
- List notifications
List change notifications, optionally filtered by monitor (taskId) and date range.
- Update monitor
Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
Action
Get agencyGet details for a transit agency.
- Get calendar
Get service calendar information for a service id.
- Get canceled trip summary
Get a summary of canceled trips.
- Get route
Get details for a specific route on an agency.
- Get route details
Get detailed information for a route by route code.
- Get route overview
Get a summary overview of an agency's routes.
- Get stop
Get details for a specific transit stop.
- List calendar dates
List calendar date exceptions (added/removed service dates).
- List routes
List all transit routes across agencies.
- List route stops
List the stops served along a route.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.