Connect Samsara and Wachete

Both apps 27Samsara 18Wachete 9

• Trigger
  New Document Submitted

  Triggers when a driver submits a new document in Samsara (documents created in the last 7 days are checked).

• Trigger
  New Route Added

  Triggers when a new route is added in Samsara (routes scheduled from 7 days ago to 30 days ahead are checked).

• Trigger
  New Route Job Completion

  Triggers 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 Address

  Creates an address in your Samsara organization's address book, with a circular geofence around it.

• Action
  Create Contact

  Creates a contact in your Samsara organization.

• Action
  Create Route

  Creates a route from a start address to an end address (both existing Samsara addresses), optionally assigned to a driver or vehicle.

• Action
  Delete route

  Deletes a dispatch route from your Samsara organization.

• Action
  Get document

  Returns a single driver document, including its type, status, driver, vehicle and submitted field values.

• Action
  Get vehicle

  Returns a single vehicle in your Samsara fleet, including its name, VIN, make, model, tags and external IDs.

• Action
  List addresses

  Returns the addresses (geofenced locations) in your Samsara address book, optionally filtered by tag or creation time.

• Action
  List assets

  Returns the assets (vehicles, trailers, equipment and other tracked assets) in your Samsara organization.

• Action
  List contacts

  Returns the contacts in your Samsara organization.

• Action
  List documents

  Returns driver documents submitted or updated in Samsara within a time range, optionally limited to one document type.

• Action
  List drivers

  Returns the drivers in your Samsara organization, optionally filtered by status, tags or update time.

• Action
  List routes

  Returns the routes scheduled within a time window, including their stops, driver and vehicle.

• Action
  List trailers

  Returns the trailers in your Samsara fleet, optionally filtered by tag.

• Action
  List vehicles

  Returns the vehicles in your Samsara fleet, optionally filtered by tag, attribute or creation/update time.

• Action
  Update route

  Updates an existing Samsara route's name, notes, assigned driver or assigned vehicle.

• Trigger
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  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.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.