Integration
Connect Samsara to Signatureapi
When New Document Submitted fires in Samsara, your agent runs Add ceremony in Signatureapi. 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 Signatureapi 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 Signatureapi
When New Document Submitted in Samsara
then Add ceremony in Signatureapi
When New Route Added in Samsara
then Add deliverable in Signatureapi
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 Signatureapi
Triggers and actions 3 triggers · 30 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 ceremonyCreates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
Action
Add deliverableCreates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
Action
Add envelopeCreates an envelope with documents and recipients and starts the signing process.
Action
Add uploadUploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
Action
Cancel envelopeCancel an in-progress envelope so remaining recipients can no longer sign.
Action
Delete envelopeDelete an envelope.
Action
Get deliverableRetrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
Action
Get envelopeRetrieve a single envelope by id.
Action
Get recipientRetrieves a recipient's details, including status, ceremony information and completion timestamp.
Action
Get uploadFetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
Action
List deliverablesReturns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
Action
List envelopesLists envelopes in the account, most recent first, optionally filtered by status or topic.
Action
Resend requestResends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
Action
Update envelopeUpdate mutable fields (e.g. title, metadata) of an existing envelope.
Action
Update recipientReplaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
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 Signatureapi
HubSpot to SignatureapiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SignatureapiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SignatureapiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SignatureapiGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Samsara and Signatureapi, 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 Signatureapi when something happens in Samsara?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Samsara?
Signatureapi has no triggers in the catalog today, so automations start in Samsara. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Samsara or Signatureapi?
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 Signatureapi 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.