Connect inMobile - SMS gateway to Iterable

Both apps 42inMobile - SMS gateway 19Iterable 23

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

• Action
  Add email template

  Creates an email template, or updates every email template that already has the same client template ID.

• Action
  Add list

  Creates a new static list in Iterable and returns its id.

• Action
  Add user to list

  Adds a user, identified by email or user ID, to a static Iterable list, optionally updating their profile data.

• Action
  Create a User

  Creates a user profile in Iterable (or updates it if one already exists), identified by email or user ID, with any profile data you supply.

• Action
  Delete catalog item

  Deletes an item from an Iterable catalog. Deletion is asynchronous, so the item may take a moment to disappear.

• Action
  Delete list

  Deletes a list from your Iterable project.

• Action
  Delete user

  Deletes an Iterable user by email address. Deletion is processed asynchronously.

• Action
  Get catalog item

  Returns one item from an Iterable catalog, including all of its field values.

• Action
  Get email template

  Returns an email template by its ID, including its HTML and plain-text content, subject, sender details and metadata.

• Action
  Get user

  Returns an Iterable user profile, including all its data fields, looked up by email address.

• Action
  List lists

  Returns all lists in the Iterable project, including their id, name and list type.

• Action
  List users in list

  Returns every user (email, or userId) who belongs to the chosen Iterable list.

• Action
  Remove user from list

  Removes a user, identified by email or user ID, from an Iterable static list.

• Action
  Send email

  Sends an email from an Iterable triggered campaign to a single user, identified by email address or user ID.

• Action
  Send push notification

  Sends a push notification from an existing push campaign to one Iterable user, now or at a scheduled time.

• Action
  Send SMS

  Sends an SMS from an Iterable SMS campaign to one user, identified by email or user ID, optionally scheduled for later.

• Action
  Track a Purchase

  Records a purchase for an Iterable user, with its line items and order total, and clears the user's shopping cart. Creates the user if they do not exist yet.

• Action
  Track Event

  Records a custom event against an Iterable user profile, identified by email or user ID, with optional event data.

• Action
  Trigger campaign

  Sends an existing triggered campaign to the members of one or more lists.

• Action
  Update a User

  Updates a user's profile data in Iterable, creating the user if none exists. Data is merged, so fields you leave out are kept.

• Action
  Update a User's Shopping Cart Items

  Replaces the shopping cart items stored on an Iterable user profile, creating the user if they do not exist yet.

• Action
  Update catalog item

  Creates or updates a catalog item, changing only the fields you provide and leaving other fields as they are. Iterable applies the change asynchronously.

• Action
  Update user subscriptions

  Updates a user's list, channel and message type subscriptions in Iterable. Any subscription list you provide replaces the user's existing one.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.