Connect inMobile - SMS gateway and Wachete

Both apps 28inMobile - SMS gateway 19Wachete 9

• Trigger
  New email event

  Triggers when a new email event occurs on a message you sent, such as delivered, opened, clicked, bounced or unsubscribed.

• Trigger
  New incoming RCS message

  Triggers when a new RCS message is received by one of your inMobile RCS agents, including text, file, location and suggestion responses.

• Trigger
  New incoming SMS message

  Triggers when a new SMS message is received on one of your inMobile numbers.

• Trigger
  New SMS status report

  Triggers when a delivery status report arrives for a sent SMS message. inMobile hands out each report only once, so a report collected by this trigger can't be retrieved again through the API.

• Action
  Add list

  Creates a new recipient list in your inMobile account and returns its id, name and creation time.

• Action
  Add Mobile Number to Blacklist

  Adds a mobile number to the inMobile blacklist so it no longer receives messages, and returns the created blacklist entry.

• Action
  Add recipient

  Creates a recipient with a phone number and optional contact details on an inMobile SMS list, and returns the new recipient.

• Action
  Cancel SMS message

  Cancels scheduled SMS messages that have not been sent yet and returns a result for each message.

• Action
  Create or Update Contact

  Creates a recipient on an inMobile list, or updates the existing recipient on that list with the same phone number.

• Action
  Delete Contact

  Deletes a contact (recipient) from an inMobile list.

• Action
  Find recipient by number

  Returns the recipient on an inMobile list that has the specified phone number, and reports whether one was found.

• Action
  List lists

  Returns all recipient lists in the inMobile account, with each list's id, name and creation time.

• Action
  List recipients

  Returns all recipients in an inMobile list, including their phone numbers and fields.

• Action
  Parse phone numbers

  Checks a list of phone numbers and returns, for each one, whether it is valid along with its cleaned number, country code and local number.

• Action
  Remove Mobile Number From Blacklist

  Removes a mobile number from your inMobile blacklist, so it can receive messages again.

• Action
  Send email

  Sends an email with a subject and HTML body to up to 100 recipients through inMobile, optionally scheduled for later, and returns the message id and accepted recipients.

• Action
  Send RCS text message

  Sends a text-only RCS message from one of your RCS agents to a mobile number, with optional suggested replies and actions. Returns the message id and the parsed recipient number.

• Action
  Send SMS Message

  Sends one SMS text message to a mobile number, immediately or at a scheduled time, and returns the message ID and how many SMS parts it uses.

• Action
  Update recipient

  Updates an existing recipient on an inMobile list. Only the details you fill in are changed; anything left blank keeps its current value.

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