Connect SMS Manager by BulkSMS.com.au and Wachete

Both apps 17SMS Manager by BulkSMS.com.au 8Wachete 9

• Trigger
  New Delivery Receipt

  Triggers when a delivery receipt arrives for an SMS, MMS or WhatsApp message you sent.

• Trigger
  New Incoming MMS

  Triggers when an MMS is received on one of your inbound numbers, with its sender, text and image links.

• Trigger
  New Incoming SMS

  Triggers when an SMS is received on one of your inbound numbers.

• Action
  Get Message

  Returns the summary of a sent message — sender, text, status, recipient count and cost — looked up by its message reference.

• Action
  Get Simulated Message Status

  Returns the status of a message simulated from a demo handset: queued, processing, processed (with the received message's id) or failed.

• Action
  Send MMS

  Sends an MMS (picture message) to one or more phone numbers, contacts or groups, and returns the message reference and cost.

• Action
  Send SMS

  Sends an SMS text message to one or more phone numbers, contacts or groups.

• Action
  Simulate Incoming Message from Demo Handset

  Sends a free simulated SMS, MMS or WhatsApp message from a demo handset into your account, firing the same webhooks a real message does.

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