Integration
Connect Bart to Knock
When New service advisory fires in Bart, your agent runs Add user in Knock. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Bart and Knock to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Bart can start in Knock
When New service advisory in Bart
then Add user in Knock
When New service advisory in Bart
then Get user in Knock
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Bart and Knock
Triggers and actions 1 trigger · 16 actions
Trigger
New service advisoryTriggers when BART posts a new service advisory (delay, emergency or information notice).
Action
Find trips by origin and destinationFinds BART trips departing from an origin station to a destination station around a given time, with fares and legs for each trip.
Action
Get routeReturns details for a BART route: its name, colour, origin and destination, and the ordered list of stations it serves.
Action
Get stationReturns detailed information about a BART station, including its address, location, routes, platforms and nearby attractions.
Action
Get station scheduleReturns the full day's scheduled train departures from a BART station, with line, destination, time and platform for each.
Action
List real-time departuresReturns the current estimated departure times for trains leaving a BART station, grouped by destination.
Action
List routesReturns the list of BART routes (lines) in service for the current or a chosen schedule date.
Action
List service advisoriesReturns BART's current service advisories (delays, emergencies and general information).
Action
List stationsReturns every BART station with its full name, abbreviation, coordinates and address.
Action
Add objectCreates an object in a Knock collection, or updates it if an object with that ID already exists, setting its name, locale, time zone, custom properties, channel data and preferences.
Action
Add userCreate a user in Knock, or update an existing one with the same user id (only the supplied properties change).
Action
Delete objectPermanently removes an object from the specified collection. This cannot be undone.
Action
Delete userPermanently delete a Knock user and all associated data.
Action
Get objectRetrieves a specific object by its ID from a collection, including all of its custom properties.
Action
Get userRetrieve a single Knock user by id.
Action
List objectsLists the objects in a Knock collection, optionally with their preferences.
Action
List usersList all users in the Knock account, paginated.
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
What our customers say
More from Bart
Bart to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bart to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bart to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bart to Google SheetsGoogle Sheets
Bart to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bart to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Knock
EquipDash to KnockEquipDash is a AI-powered equipment rental and tour booking software built for outdoor recreation operators.
HubSpot to KnockHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to KnockSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to KnockSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to KnockGoogle Sheets
Gmail to KnockGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Bart and Knock, answered
What can start an automation from Bart?
Any of Bart's 1 trigger in the catalog, including New service advisory. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Knock when something happens in Bart?
Any of Knock's 8 actions, including Add object, Add user, Get object and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Knock to Bart?
Knock has no triggers in the catalog today, so automations start in Bart. If you need the other direction, ask: your agent reads Knock's API documentation and adds it.
Do I have to build a connector for Bart or Knock?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.