Connect Funnel-Tunnel and Wachete

Both apps 17Funnel-Tunnel 8Wachete 9

• Trigger
  Contact Updated

  Triggers when an existing contact updated.

• Trigger
  New Product Created

  Triggers when a new product created.

• Trigger
  Product Updated

  Triggers when an existing product updated.

• Action
  Create Contact

  Creates a contact in your Funnel-Tunnel website CRM. If a contact with the same email already exists, it is updated with the supplied values.

• Action
  Create Product

  Creates a store product on your website, optionally updating an existing product with the same URL instead.

• Action
  Find Contact

  Finds a contact on your website by email address and returns the contact's details.

• Action
  Find Product

  Finds store products whose title contains the given text, optionally limited to one category. Returns the matching products and the first match.

• Action
  Update Product

  Updates an existing product in your store. Only the fields you fill in are changed.

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