Connect Ubidots and Wachete

Both apps 27Ubidots 18Wachete 9

• Trigger
  Device Is Updated

  Triggers when a device is created or any of its fields (name, description, tags, properties, organization, status) changes.

• Trigger
  Event Is Triggered

  Triggers when a chosen Ubidots event fires, returning the new log entry for that event.

• Trigger
  Variable Updated

  Triggers when a variable is created or its settings (name, description, unit, tags, properties) change.

• Action
  Add device

  Creates a new device in your Ubidots account.

• Action
  Add event

  Creates a new Ubidots event (alert rule) with its triggers, actions and active schedule.

• Action
  Add variable

  Creates a new variable on a Ubidots device.

• Action
  Create Dot

  Sends a single Dot (a value with optional timestamp and context) to a variable on a device. The device and variable are created automatically if they do not exist.

• Action
  Create Multiple Dots on Same Device

  Sends values to one or more variables of a Ubidots device in a single call, creating the device and variables if they do not exist.

• Action
  Delete device

  Permanently deletes a device and its variables from your Ubidots account.

• Action
  Delete variable

  Permanently deletes a variable and its data from Ubidots.

• Action
  Get data series

  Returns time-series values for one or more variables over a time range, each with its device and variable details.

• Action
  Get device

  Returns a single Ubidots device, looked up by its ID or label.

• Action
  Get device last values

  Returns the most recent value of every variable on a Ubidots device.

• Action
  Get variable

  Returns a single Ubidots variable, including its device, unit, tags, properties and last value.

• Action
  List devices

  Returns the devices in your Ubidots account, with their labels, names, tags and activity details.

• Action
  List variables

  Returns the variables in the Ubidots account, each with its device, label, name, type, unit and last value.

• Action
  Update device

  Updates the specified fields of an existing Ubidots device, such as its name, label, description, tags, properties or organization, and returns the updated device.

• Action
  Update variable

  Updates the specified fields of an existing Ubidots variable, such as its name, label, unit, tags or description. Returns the updated variable.

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