Connect Userflow and Wachete

Both apps 28Userflow 19Wachete 9

• Trigger
  Checklist Completed

  Triggered when a user finishes every task in a Userflow checklist.

• Trigger
  Checklist Dismissed/Ended

  Triggered when a Userflow checklist ends for a user — because they dismissed it, it was completed, or it stopped applying to them. The reason is in checklist_end_reason.

• Trigger
  Checklist Started

  Triggered when a user starts a Userflow checklist. Why it started is in checklist_start_reason.

• Trigger
  Checklist Task Completed

  Triggered when a user completes a single task inside a Userflow checklist.

• Trigger
  Event Tracked

  Triggered when Userflow tracks an event for a user — either your own custom events or Userflow's own flow and checklist events. Name one event to watch, or leave it blank to fire for all of them.

• Trigger
  Flow Completed

  Triggered when a user completes a Userflow flow by reaching its goal step.

• Trigger
  Flow Dismissed/Ended

  Triggered when a Userflow flow ends for a user — because they dismissed it, finished it, or it stopped applying. The reason is in flow_end_reason.

• Trigger
  Flow Started

  Triggered when a user starts a Userflow flow. Why it started is in flow_start_reason.

• Trigger
  Group Created/Updated

  Triggered when a group (a company or account) is created or changed in Userflow.

• Trigger
  Launcher Activated

  Triggered when a user clicks a Userflow launcher (a beacon, button or hotspot) to open it.

• Trigger
  Launcher Dismissed

  Triggered when a user dismisses a Userflow launcher (a beacon, button or hotspot).

• Trigger
  Launcher Seen

  Triggered when a Userflow launcher (a beacon, button or hotspot) is shown to a user.

• Trigger
  Question Answered

  Triggered when a user answers a question in a Userflow flow — a survey, NPS or rating step. The answer arrives as text, a number, or a list depending on the question type.

• Trigger
  User Created/Updated

  Triggered when a user is created or changed in Userflow.

• Action
  Create/Update Group

  Creates a group (a company or account) in Userflow, or updates it if a group with that ID already exists. Only the attributes you send are changed.

• Action
  Create/Update User

  Creates a user in Userflow, or updates them if a user with that ID already exists. Only the attributes you send are changed. Optionally adds the user to a group.

• Action
  Find Group

  Finds groups (companies or accounts) in Userflow by name. Userflow's API cannot filter on the server, so this reads up to 300 groups and matches them here; leave the name blank to just list them.

• Action
  Find User

  Finds users in Userflow by email or name. Userflow's API cannot filter on the server, so this reads up to 300 users and matches them here; leave both fields blank to just list them.

• Action
  Track Event

  Tracks an event for a user in Userflow, so you can use it to start flows or checklists and to segment users.

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