Integration
Connect LumApps to touchSMS
When New Comment fires in LumApps, your agent runs Create Contact in touchSMS. 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 LumApps and touchSMS 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 LumApps can start in touchSMS
When New Comment in LumApps
then Create Contact in touchSMS
When New Community Post in LumApps
then Get account in touchSMS
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 LumApps and touchSMS
Triggers and actions 5 triggers · 15 actions
Trigger
New CommentTriggers when a new comment is added to a LumApps content item or community post.
Trigger
New Community PostTriggers when a new post is published in a LumApps community.
Trigger
New NotificationTriggers when the connected user receives a new LumApps notification.
Trigger
New Published ContentTriggers when a content item (page or news) is published in LumApps.
Trigger
New UserTriggers when a new user is added to the LumApps platform.
Action
Create CommentAdds a comment, or a reply to a comment, on a LumApps content item or community post.
Action
Create Community PostCreates a post in a LumApps community.
Action
Create NotificationSends a custom in-app notification to a user or groups in LumApps.
Action
Delete Community PostDeletes a LumApps community post.
Action
Delete ContentDeletes a LumApps content item (page or news).
Action
Find a CommunityFinds communities whose title matches the search text and returns the first match.
Action
Get CommunityReturns a LumApps community by its ID.
Action
Get Community PostReturns a LumApps community post by its ID.
Action
Get ContentReturns a LumApps content item (page, news, article) by its ID.
Action
Get GroupReturns a LumApps user group by its ID.
Action
Get SiteReturns a LumApps site by its ID.
Action
Get UserReturns a LumApps user by email address or ID.
Action
Update Group MembersAdds users to and removes users from a LumApps group.
Action
Create ContactCreates a contact in touchSMS, optionally adding it to a contact group.
Action
Get accountRetrieves the touchSMS account details for the connected API key, including the user's email and current credit balance.
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 LumApps
LumApps to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LumApps to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LumApps to MailchimpMailchimp marketing automation and email platform.
LumApps to StripeStripe is a payment processing platform for online businesses.
LumApps to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LumApps to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into touchSMS
Apex27 to touchSMSApex27 is a full-featured estate agent CRM platform
Balabook to touchSMSBalabook is an accounting software for business owners and accounting firms to help improve the financial...
SmartrMail to touchSMSSmartrMail is the easiest way to send your customers the products they’re most likely to buy.
HubSpot to touchSMSHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to touchSMSSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to touchSMSSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Questions
LumApps and touchSMS, answered
What can start an automation from LumApps?
Any of LumApps's 5 triggers in the catalog, including New Comment, New Community Post, New Notification and New Published Content. Describe the moment in plain language and your agent picks the right one.
What can your agent do in touchSMS when something happens in LumApps?
Any of touchSMS's 2 actions, including Create Contact and Get account. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from touchSMS to LumApps?
touchSMS has no triggers in the catalog today, so automations start in LumApps. If you need the other direction, ask: your agent reads touchSMS's API documentation and adds it.
Do I have to build a connector for LumApps or touchSMS?
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 LumApps and touchSMS 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.