---
title: "Connect inMobile - SMS gateway to Luma - APIANT.ai"
description: "When \"New email event\" fires in inMobile - SMS gateway, your agent runs \"Add event\" in Luma."
canonical: "https://apiant.ai/connect/inmobile-sms-gateway-to-luma"
---

# Connect inMobile - SMS gateway to Luma

When **New email event** fires in [inMobile - SMS gateway](https://apiant.ai/connections/inmobile-sms-gateway), your agent runs **Add event** in [Luma](https://apiant.ai/connections/luma). 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 Luma **19** 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 Luma 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 Luma

- When **New email event** in inMobile - SMS gateway then **Add event** in Luma
- When **New incoming RCS message** in inMobile - SMS gateway then **Add ticket type** in Luma

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 Luma

## Triggers and actions 4 triggers · 34 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 event**

Adds an existing event to your Luma calendar — either a Luma event you manage or an event hosted on another platform. The event is approved right away unless you choose to keep it pending for admin review.

- Action

**Add guests**

Adds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.

- Action

**Add host**

Adds a host to a Luma event, as a manager or as check-in staff, by email address.

- Action

**Add ticket type**

Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.

- Action

**Apply contact tag**

Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.

- Action

**Block contact**

Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.

- Action

**Cancel event**

Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.

- Action

**Create Calendar Person**

Adds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.

- Action

**Get calendar**

Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.

- Action

**Get event**

Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.

- Action

**Get guest**

Returns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.

- Action

**Import contacts**

Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.

- Action

**List contacts**

Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.

- Action

**List events**

Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.

- Action

**List guests**

Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.

- Action

**List ticket types**

Returns every ticket type set up for a Luma event, including its name, price and capacity.

- Action

**Send invites**

Sends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.

- Action

**Update event**

Updates an existing Luma event's details, such as its name, time, location, description, capacity, registration settings and page appearance. Fields left blank keep their current values.

- Action

**Update guest status**

Changes a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.

## 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)
- [ **Luma** Luma is an event management app that gives you the tools to host delightful events.](https://apiant.ai/connections/luma)

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 Luma

- [ **HubSpot to Luma** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-luma)
- [ **Salesforce to Luma** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-luma)
- [ **Slack to Luma** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-luma)
- [ **Google Sheets to Luma** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-luma)
- [ **Gmail to Luma** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-luma)
- [ **Google Calendar to Luma** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-luma)

Questions

## inMobile - SMS gateway and Luma, 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 Luma when something happens in inMobile - SMS gateway?

Any of Luma's 19 actions, including Create Calendar Person, Send invites, Update event and Update guest status. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Luma to inMobile - SMS gateway?

Luma has no triggers in the catalog today, so automations start in inMobile - SMS gateway. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.

###

### Do I have to build a connector for inMobile - SMS gateway or Luma?

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