Connect Domo and Wachete

Both apps 37Domo 28Wachete 9

• Trigger
  New DataSet

  Triggers when a new DataSet is created in your Domo instance.

• Trigger
  New User

  Triggers when a new user is added to your Domo instance.

• Action
  Add User to Group

  Adds a Domo user to a group.

• Action
  Create Group

  Creates a new group in Domo and returns its ID.

• Action
  Create Project

  Creates a Domo project with its members.

• Action
  Create User

  Creates a Domo user with a name, email and role, optionally sending them an invite.

• Action
  Delete DataSet

  Permanently deletes a Domo DataSet.

• Action
  Delete Group

  Deletes a Domo group.

• Action
  Delete Page

  Deletes a Domo page.

• Action
  Delete Project

  Deletes a Domo project.

• Action
  Get DataSet

  Returns one Domo DataSet's details: name, row and column counts, schema and timestamps.

• Action
  Get Group

  Returns one Domo group by its ID, with its name, active flag and member count.

• Action
  Get Page

  Returns one Domo page with its name, parent, cards and visibility.

• Action
  Get Project

  Returns one Domo project with its name, members and creator.

• Action
  Get User

  Returns one Domo user by ID, including name, email, role and title.

• Action
  Import Data into DataSet

  Loads CSV rows into a Domo DataSet, replacing its data or appending to it.

• Action
  List Activity Log Entries

  Returns Domo activity log entries (who did what, and when) for a time range.

• Action
  List DataSets

  Returns DataSets in your Domo instance, optionally filtered by name.

• Action
  List Groups

  Returns the groups in your Domo instance, with each group's name and member count.

• Action
  List Group Users

  Returns the IDs of the users in a Domo group.

• Action
  List Pages

  Returns the pages in your Domo instance with their child pages.

• Action
  List Projects

  Returns all projects in your Domo instance.

• Action
  List Users

  Returns the users in your Domo instance.

• Action
  Query DataSet

  Runs a SQL query against a Domo DataSet and returns the matching columns and rows.

• Action
  Remove User from Group

  Removes a Domo user from a group.

• Action
  Update DataSet

  Updates a Domo DataSet's name or description.

• Action
  Update Project

  Updates a Domo project's name, description, visibility or due date.

• Action
  Update User

  Updates a Domo user's name, email, role, title, phone or location.

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