Integration
Connect Samsara to Wasi
When New Document Submitted fires in Samsara, your agent runs Add Contact in Wasi. 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 Samsara and Wasi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Samsara can start in Wasi
When New Document Submitted in Samsara
then Add Contact in Wasi
When New Route Added in Samsara
then Add task in Wasi
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 Samsara and Wasi
Triggers and actions 3 triggers · 27 actions
Trigger
New Document SubmittedTriggers when a driver submits a new document in Samsara (documents created in the last 7 days are checked).
Trigger
New Route AddedTriggers when a new route is added in Samsara (routes scheduled from 7 days ago to 30 days ahead are checked).
Trigger
New Route Job CompletionTriggers on each new route stop event in Samsara (arrived, departed/completed, skipped, and other stop updates); the event name is in the operation field, so filter on it for completions.
Action
Create AddressCreates an address in your Samsara organization's address book, with a circular geofence around it.
Action
Create ContactCreates a contact in your Samsara organization.
Action
Create RouteCreates a route from a start address to an end address (both existing Samsara addresses), optionally assigned to a driver or vehicle.
Action
Delete routeDeletes a dispatch route from your Samsara organization.
Action
Get documentReturns a single driver document, including its type, status, driver, vehicle and submitted field values.
Action
Get vehicleReturns a single vehicle in your Samsara fleet, including its name, VIN, make, model, tags and external IDs.
Action
List addressesReturns the addresses (geofenced locations) in your Samsara address book, optionally filtered by tag or creation time.
Action
List assetsReturns the assets (vehicles, trailers, equipment and other tracked assets) in your Samsara organization.
Action
List contactsReturns the contacts in your Samsara organization.
Action
List documentsReturns driver documents submitted or updated in Samsara within a time range, optionally limited to one document type.
Action
List driversReturns the drivers in your Samsara organization, optionally filtered by status, tags or update time.
Action
List routesReturns the routes scheduled within a time window, including their stops, driver and vehicle.
Action
List trailersReturns the trailers in your Samsara fleet, optionally filtered by tag.
Action
List vehiclesReturns the vehicles in your Samsara fleet, optionally filtered by tag, attribute or creation/update time.
Action
Update routeUpdates an existing Samsara route's name, notes, assigned driver or assigned vehicle.
Action
Add ContactRegisters a contact from a client in Wasi, creating the client if they do not already exist, and optionally associates them with a property.
Action
Add propertyCreates a new property listing in Wasi and returns its id.
Action
Add taskCreates a task (call, meeting, visit, etc.) in a Wasi user's schedule.
Action
Delete taskDeletes a task from a user's schedule in Wasi, identified by its id and assigned date.
Action
Get clientReturns a single Wasi client, including contact details, location, client types and tags.
Action
Get propertyReturns a single Wasi property by its id, including its location, prices, images and features.
Action
Get taskReturns one task from the Wasi schedule, including its type, status, assigned user and linked clients and properties.
Action
Get userReturns a Wasi user (employee) by id, including name, email, role and contact details.
Action
List tasksReturns the tasks on a user's Wasi schedule between a start and end date, optionally limited to one task type.
Action
List usersReturns all users (agents and administrators) of your Wasi company, with their email, type and profile details.
Action
Update propertyUpdates an existing Wasi property. Only the fields you fill in are changed.
Action
Update taskUpdates an existing task in the Wasi schedule, changing only the fields you fill in.
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 Samsara
Samsara to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Samsara to StripeStripe is a payment processing platform for online businesses.
Samsara to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Samsara to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Samsara to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Samsara to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
More into Wasi
Vercel to WasiVercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.
HubSpot to WasiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WasiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WasiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WasiGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to WasiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Samsara and Wasi, answered
What can start an automation from Samsara?
Any of Samsara's 3 triggers in the catalog, including New Document Submitted, New Route Added and New Route Job Completion. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wasi when something happens in Samsara?
Any of Wasi's 12 actions, including Update property, Update task, Add Contact and Add property. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wasi to Samsara?
Wasi has no triggers in the catalog today, so automations start in Samsara. If you need the other direction, ask: your agent reads Wasi's API documentation and adds it.
Do I have to build a connector for Samsara or Wasi?
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.
Can my AI client use Samsara and Wasi without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.