Integration
Connect inMobile - SMS gateway and QuickBase
When New email event fires in inMobile - SMS gateway, your agent runs Insert or update records in QuickBase, or New or updated record in QuickBase to Create or Update Contact in inMobile - SMS gateway. 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 QuickBase 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 and QuickBase can do together
From inMobile - SMS gateway to QuickBase
When New email event in inMobile - SMS gateway
then Insert or update records in QuickBase
When New incoming RCS message in inMobile - SMS gateway
then Query records in QuickBase
From QuickBase to inMobile - SMS gateway
When New or updated record in QuickBase
then Create or Update Contact in inMobile - SMS gateway
When New record in QuickBase
then Send email in inMobile - SMS gateway
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 QuickBase
Triggers and actions 6 triggers · 36 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.
Trigger
New or updated recordPolling trigger. Fires for each record added or modified in the specified Quickbase table, ordered by Date Modified. Records are deduped by their Record ID# (field 3).
Trigger
New recordPolling trigger. Fires for each new record added to the specified Quickbase table, ordered by Record ID#. Records are deduped by their Record ID# (field 3).
Action
Add appCreates a new Quickbase application in the connected realm, optionally with a description, app variables and security properties.
Action
Add fieldCreates a new field in a Quickbase table, optionally with display settings, type-specific properties and per-role permissions.
Action
Add tableCreate a new table in a QuickBase app.
Action
Delete appDelete a QuickBase app by id.
Action
Delete fieldDelete one or more QuickBase fields from a table.
Action
Delete recordsDelete records from a Quickbase table that match a query (Quickbase query language in the where clause).
Action
Delete tableDeletes a table from a Quickbase app, including all of the data within it.
Action
Get appGet the properties of a Quickbase application by its app ID.
Action
Get fieldGet a single QuickBase field by id.
Action
Get reportGet metadata for a single QuickBase report.
Action
Get tableGet the properties of a single Quickbase table by table ID and app ID.
Action
Get table fieldsList all fields (columns) for a Quickbase table, including field IDs, labels, and types.
Action
Get tables for appList all tables belonging to a Quickbase application.
Action
Insert or update recordsInsert new records or update existing ones in a Quickbase table. Pass data as an array of record objects keyed by field ID. Include the table's key field (or record ID field 3) to update; omit to insert.
Action
List reportsLists all reports defined on a Quickbase table.
Action
Query recordsQuery records from a Quickbase table. Optionally pass select (array of field IDs), where (Quickbase query language), sortBy, groupBy, and options (skip/top).
Action
Run formulaRuns a Quickbase formula against a table (and optionally a record) and returns the result as text.
Action
Run reportRun a Quickbase report by report ID and table ID and return its result rows.
Action
Update appUpdates an app's name, description, app variables and/or security properties. Properties left blank stay unchanged.
Action
Update fieldUpdates the properties and per-role permissions of an existing field in a Quickbase table. Properties left blank stay unchanged.
Action
Update tableUpdate an existing QuickBase table's properties.
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 QuickBase
HubSpot to QuickBaseHubSpot is your all-in-one stop for all of your marketing software needs.
Mailchimp to QuickBaseMailchimp marketing automation and email platform.
Pipedrive to QuickBasePipedrive is a sales CRM and pipeline management tool.
JIRA to QuickBaseAtlassian JIRA Cloud — issue tracking and project management.
Klaviyo to QuickBaseKlaviyo is a marketing automation platform for email and SMS.
JotForm to QuickBaseJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
Questions
inMobile - SMS gateway and QuickBase, 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 QuickBase when something happens in inMobile - SMS gateway?
Any of QuickBase's 21 actions, including Update app, Update field, Update table and Add app. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from QuickBase to inMobile - SMS gateway?
Yes. When something happens in QuickBase, your agent can act in inMobile - SMS gateway too. This page covers both directions: QuickBase's triggers and inMobile - SMS gateway's actions are listed here as well.
Do I have to build a connector for inMobile - SMS gateway or QuickBase?
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 QuickBase 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.