Connect Bento and Wachete

Both apps 33Bento 24Wachete 9

• Trigger
  New Tag

  Triggers when a new tag is created on your Bento site.

• Action
  Add broadcast

  Creates a broadcast email draft in Bento, optionally scheduled and approved for sending to tagged or segmented subscribers.

• Action
  Create Field

  Creates a custom subscriber field on your Bento site.

• Action
  Create or Update User

  Creates a Bento subscriber, or updates the name of an existing one, by email address.

• Action
  Create or Update User and Apply Tag

  Creates or updates a Bento subscriber by email and applies one or more tags, without triggering Flows.

• Action
  Create or Update User and Apply Tag (Trigger Flows)

  Applies a tag to a Bento subscriber (creating them if needed) through an event, so any Flows listening for that tag start.

• Action
  Create Tag

  Creates a tag on your Bento site.

• Action
  Delete tag

  Discards a tag in Bento by name (running it on an already-discarded tag restores it).

• Action
  Fetch Site Metrics

  Returns your Bento site's user, subscriber and unsubscriber counts.

• Action
  Fetch Subscriber

  Returns a Bento subscriber's details, tags and custom fields by email address.

• Action
  Get email template

  Returns one email template, including its name, subject and HTML content.

• Action
  Get segment

  Returns one segment, including its name, description and filter definition.

• Action
  Import subscribers

  Queues up to 1,000 subscribers for import or update in Bento. Imports do not trigger automations.

• Action
  List Broadcasts

  Returns one page of Bento broadcasts with the chosen status, including their send stats.

• Action
  List Fields

  Returns every custom subscriber field on your Bento site.

• Action
  List segments

  Returns all segments in your Bento site.

• Action
  List sequences

  Returns the sequences on your Bento site, including each sequence's email templates.

• Action
  List Tags

  Returns every tag on your Bento site.

• Action
  List workflows

  Returns all workflows on the Bento site, with their name, status and email templates.

• Action
  Remove Tag from Subscriber

  Removes a tag from a Bento subscriber by email.

• Action
  Track Subscribe Event

  Subscribes or unsubscribes a Bento subscriber by email.

• Action
  Update email template

  Updates the subject, HTML content, or editor type of a Bento email template.

• Action
  Update Subscriber Field

  Sets one custom field value on a Bento subscriber.

• Action
  Validate Email

  Checks whether an email address looks valid and deliverable.

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