Integration
Connect inMobile - SMS gateway to Luma
When New email event fires in inMobile - SMS gateway, your agent runs Add event in Luma. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want inMobile - SMS gateway and Luma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)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 eventTriggers when a new email event occurs on a message you sent, such as delivered, opened, clicked, bounced or unsubscribed.
Trigger
New incoming RCS messageTriggers 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 messageTriggers when a new SMS message is received on one of your inMobile numbers.
Trigger
New SMS status reportTriggers 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 listCreates a new recipient list in your inMobile account and returns its id, name and creation time.
Action
Add Mobile Number to BlacklistAdds a mobile number to the inMobile blacklist so it no longer receives messages, and returns the created blacklist entry.
Action
Add recipientCreates a recipient with a phone number and optional contact details on an inMobile SMS list, and returns the new recipient.
Action
Cancel SMS messageCancels scheduled SMS messages that have not been sent yet and returns a result for each message.
Action
Create or Update ContactCreates a recipient on an inMobile list, or updates the existing recipient on that list with the same phone number.
Action
Delete ContactDeletes a contact (recipient) from an inMobile list.
Action
Find recipient by numberReturns the recipient on an inMobile list that has the specified phone number, and reports whether one was found.
Action
List listsReturns all recipient lists in the inMobile account, with each list's id, name and creation time.
Action
List recipientsReturns all recipients in an inMobile list, including their phone numbers and fields.
Action
Parse phone numbersChecks 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 BlacklistRemoves a mobile number from your inMobile blacklist, so it can receive messages again.
Action
Send emailSends 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 messageSends 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 MessageSends 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 recipientUpdates an existing recipient on an inMobile list. Only the details you fill in are changed; anything left blank keeps its current value.
Action
Add eventAdds 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 guestsAdds 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 hostAdds a host to a Luma event, as a manager or as check-in staff, by email address.
Action
Add ticket typeCreates 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 tagApplies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
Action
Block contactBlocks 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 eventCancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
Action
Create Calendar PersonAdds 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 calendarReturns 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 eventReturns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
Action
Get guestReturns 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 contactsImports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
Action
List contactsReturns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
Action
List eventsReturns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
Action
List guestsReturns 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 typesReturns every ticket type set up for a Luma event, including its name, price and capacity.
Action
Send invitesSends 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 eventUpdates 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 statusChanges 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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from inMobile - SMS gateway
inMobile - SMS gateway to MailercloudMailercloud is a cloud-based email marketing platform that allows businesses to launch email marketing...
inMobile - SMS gateway to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
inMobile - SMS gateway to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
inMobile - SMS gateway to MailchimpMailchimp marketing automation and email platform.
inMobile - SMS gateway to StripeStripe is a payment processing platform for online businesses.
inMobile - SMS gateway to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LumaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LumaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LumaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LumaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LumaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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.