--- title: "Connect inMobile - SMS gateway to Resend - APIANT.ai" description: "When \"New email event\" fires in inMobile - SMS gateway, your agent runs \"Send Email\" in Resend." canonical: "https://apiant.ai/connect/inmobile-sms-gateway-to-resend" --- # Connect inMobile - SMS gateway to Resend When **New email event** fires in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), your agent runs **Send Email** in [Resend](https://apiant.ai/connections/resend). Describe the whole flow and it is built, tested on every scenario and kept running. inMobile - SMS gateway **4** triggers inMobile - SMS gateway **15** actions Resend **28** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want inMobile - SMS gateway and Resend to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What inMobile - SMS gateway can start in Resend - When **New email event** in inMobile - SMS gateway then **Send Email** in Resend - When **New incoming RCS message** in inMobile - SMS gateway then **Add Contact to Segment** in Resend Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with inMobile - SMS gateway and Resend ## Triggers and actions 4 triggers ยท 43 actions - 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 Contact to Segment** Adds a contact to a Resend segment. You can identify the contact by its ID or email address. - Action **Add Suppression** Adds an email address to your Resend suppression list so no further mail is sent to it. - Action **Cancel Email** Cancels a scheduled Resend email that has not been sent yet. - Action **Create API Key** Creates a new Resend API key. The key itself is returned once, so store it right away. - Action **Create Contact** Creates a contact in Resend. Returns the new contact's ID. - Action **Create Domain** Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it. - Action **Create Segment** Creates a new segment in Resend for grouping contacts. - Action **Delete API Key** Deletes a Resend API key so it can no longer be used. - Action **Delete Contact** Deletes a contact from Resend. You can identify the contact by its ID or email address. - Action **Delete Domain** Removes a sending domain from Resend. - Action **Delete Segment** Deletes a segment from Resend. The contacts themselves are not deleted. - Action **List API Keys** Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned. - Action **List Contacts** Returns the contacts in your Resend account, optionally limited to one segment. - Action **List Domains** Returns the sending domains on your Resend account and each one's verification status. - Action **List Segments** Returns the contact segments in your Resend account. - Action **List Sent Emails** Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id. - Action **List Suppressions** Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added. - Action **Remove Contact From Segment** Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted. - Action **Remove Suppression** Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself. - Action **Retrieve Contact** Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address. - Action **Retrieve Domain** Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status. - Action **Retrieve Segment** Returns one of your Resend segments by its ID, with the segment's name and when it was created. - Action **Retrieve Sent Email** Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event. - Action **Send Batch Emails** Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created. - Action **Send Email** Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time. - Action **Update Contact** Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is. - Action **Update Email** Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed. - Action **Verify Domain** Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes. ## Each app on its own - [ **inMobile - SMS gateway** inMobile is a powerful SMS gateway. inMobile makes it easy for you to send personalized SMS messages, manage...](https://apiant.ai/connections/inmobile-sms-gateway) - [ **Resend** Resend is the email API for developers. It's designed for you to build, test, and send transactional and...](https://apiant.ai/connections/resend) Reviews ## What our customers say ## More from inMobile - SMS gateway - [ **inMobile - SMS gateway to Mailercloud** Mailercloud is a cloud-based email marketing platform that allows businesses to launch email marketing...](https://apiant.ai/connect/inmobile-sms-gateway-to-mailercloud) - [ **inMobile - SMS gateway to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-salesforce) - [ **inMobile - SMS gateway to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/inmobile-sms-gateway-to-slack) - [ **inMobile - SMS gateway to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/inmobile-sms-gateway-to-mailchimp) - [ **inMobile - SMS gateway to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/inmobile-sms-gateway-to-stripe) - [ **inMobile - SMS gateway to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/inmobile-sms-gateway-to-shopify) ## More into Resend - [ **Documenso to Resend** Documenso is an open-source digital signing platform.](https://apiant.ai/connect/documenso-to-resend) - [ **Google BigQuery to Resend** BigQuery is Google's serverless and highly scalable enterprise data warehouse, designed to make all your...](https://apiant.ai/connect/google-bigquery-to-resend) - [ **HubSpot to Resend** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-resend) - [ **Salesforce to Resend** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-resend) - [ **Slack to Resend** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-resend) - [ **Google Sheets to Resend** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-resend) Questions ## inMobile - SMS gateway and Resend, answered ### ### What can start an automation from inMobile - SMS gateway? Any of inMobile - SMS gateway's 4 triggers in the catalog, including New email event, New incoming RCS message, New incoming SMS message and New SMS status report. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Resend when something happens in inMobile - SMS gateway? Any of Resend's 28 actions, including Create API Key, Create Contact, Create Domain and Create Segment. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Resend to inMobile - SMS gateway? Resend has no triggers in the catalog today, so automations start in inMobile - SMS gateway. If you need the other direction, ask: your agent reads Resend's API documentation and adds it. ### ### Do I have to build a connector for inMobile - SMS gateway or Resend? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use inMobile - SMS gateway and Resend without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.