Integration
Connect Noko and Samsara
When Entry Changed fires in Noko, your agent runs Create Contact in Samsara, or New Document Submitted in Samsara to Mark Invoice as Paid in Noko. 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 Noko and Samsara 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 Noko and Samsara can do together
From Noko to Samsara
When Entry Changed in Noko
then Create Contact in Samsara
When Invoice Changed in Noko
then Get document in Samsara
From Samsara to Noko
When New Document Submitted in Samsara
then Mark Invoice as Paid in Noko
When New Route Added in Samsara
then Create Project in Noko
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 Noko and Samsara
Triggers and actions 9 triggers · 29 actions
Trigger
Entry ChangedTriggers when a Noko time entry is created or changed.
Trigger
Invoice ChangedTriggers when a Noko invoice is created or changed.
Trigger
New EntryTriggers when a new time entry is logged in Noko.
Trigger
New ExpenseTriggers when a new expense is logged in Noko.
Trigger
New InvoiceTriggers when a new invoice is created in Noko.
Trigger
New ProjectTriggers when a new project is created in Noko.
Action
Approve EntryMarks a Noko time entry as approved.
Action
Archive ProjectArchives a Noko project.
Action
Create EntryLogs a new time entry in Noko.
Action
Create ExpenseLogs a new expense against a Noko project.
Action
Create ProjectCreates a new Noko project.
Action
Create TagsCreates one or more Noko tags.
Action
Delete EntryDeletes a Noko time entry.
Action
Find ExpenseFinds the most recent Noko expense matching the filters.
Action
Find InvoiceFinds a Noko invoice by reference, state or company.
Action
Find ProjectFinds a Noko project by name.
Action
Find UserFinds a Noko user by name or email.
Action
Get EntryReturns a single Noko time entry by its ID.
Action
Mark Invoice as PaidMarks a Noko invoice as paid.
Action
Update EntryUpdates a Noko time entry's date, minutes, description, project or user.
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.
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 Noko
Noko to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Noko to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Noko to StripeStripe is a payment processing platform for online businesses.
Noko to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Noko to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Noko to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Samsara
HubSpot to SamsaraHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SamsaraSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SamsaraGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SamsaraGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SamsaraGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SamsaraGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Noko and Samsara, answered
What can start an automation from Noko?
Any of Noko's 6 triggers in the catalog, including Entry Changed, Invoice Changed, New Entry and New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Samsara when something happens in Noko?
Any of Samsara's 15 actions, including Create Address, Create Contact , Create Route and Update route. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Samsara to Noko?
Yes. When something happens in Samsara, your agent can act in Noko too. This page covers both directions: Samsara's triggers and Noko's actions are listed here as well.
Do I have to build a connector for Noko or Samsara?
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 Noko and Samsara 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.