Connect Samsara to Screenly

Both apps 39Samsara 18Screenly 21

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

• Action
  Add Asset group

  Create a new asset group.

• Action
  Add Asset to Playlist

  Add an asset to a playlist with scheduling

• Action
  Add Label

  Creates a label in Screenly. Labels group screens and can be used to schedule playlists on them.

• Action
  Add Playlist

  Create a new playlist.

• Action
  Delete Asset

  Deletes a Screenly asset by its ID.

• Action
  Delete Asset group

  Delete an asset group.

• Action
  Delete Label

  Delete a label.

• Action
  Delete Playlist

  Delete a playlist.

• Action
  Delete Playlist item

  Remove an asset from a playlist.

• Action
  Get Asset

  Retrieve a single asset by id.

• Action
  Get Playlist

  Retrieve a single playlist by id, optionally embedding playlist_items.

• Action
  List Asset groups

  Retrieve a list of asset groups.

• Action
  List Assets

  Retrieve a list of assets.

• Action
  List Labels

  Retrieve a list of Screenly labels, optionally filtered by id, team, type or name.

• Action
  List Playlists

  Retrieve the playlists in your Screenly account, optionally filtered by id, title, predicate, priority, enabled state, transitions or creation date.

• Action
  Update Asset

  Update an asset's fields (title, duration, etc).

• Action
  Update Asset group

  Update an asset group.

• Action
  Update Label

  Update a label.

• Action
  Update Playlist

  Update a playlist's fields.

• Action
  Update Playlist item

  Update a playlist item (e.g. duration, order).

• Action
  Upload Asset

  Creates a new asset in Screenly from a URL — an image, video or web page that can then be scheduled on screens.

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