Integration
Connect Consent Kit and inMobile - SMS gateway
When Consent Updated fires in Consent Kit, your agent runs Create or Update Contact in inMobile - SMS gateway, or New email event in inMobile - SMS gateway to Get Project in Consent Kit. 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 Consent Kit and inMobile - SMS gateway 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 Consent Kit and inMobile - SMS gateway can do together
From Consent Kit to inMobile - SMS gateway
When Consent Updated in Consent Kit
then Create or Update Contact in inMobile - SMS gateway
When New Consent in Consent Kit
then Send email in inMobile - SMS gateway
From inMobile - SMS gateway to Consent Kit
When New email event in inMobile - SMS gateway
then Get Project in Consent Kit
When New incoming RCS message in inMobile - SMS gateway
then Create Data Link in Consent Kit
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 Consent Kit and inMobile - SMS gateway
Triggers and actions 10 triggers · 33 actions
Trigger
Consent AgreedTriggers when a participant agrees to a consent in Consent Kit.
Trigger
Consent DeclinedTriggers when a participant refuses a consent in Consent Kit.
Trigger
Consent UpdatedTriggers when a Consent Kit consent is created or updated.
Trigger
Data LinkedTriggers when new data is linked to a Consent Kit participant.
Trigger
New ConsentTriggers when a participant agrees to or refuses a consent in Consent Kit.
Trigger
Participant CreatedTriggers when a participant is added to a Consent Kit study, with their email and first name.
Action
Create Data LinkLinks data stored at a URL (a recording, notes, a file) to a Consent Kit participant.
Action
Create ParticipantAdds a participant to a Consent Kit study; Consent Kit uses the email to send them the consent form.
Action
Create StudyCreates a new study inside a Consent Kit project.
Action
Delete Data LinkDeletes (unlinks) a data link from its Consent Kit participant.
Action
Delete StudyDeletes a Consent Kit study.
Action
Get ConsentReturns one Consent Kit consent by ID: whether it was agreed or refused, the permissions given, and the participant.
Action
Get PanelReturns one Consent Kit panel by its ID, including how many panellists it has.
Action
Get ParticipantReturns one Consent Kit participant by ID, optionally with their email and first name.
Action
Get ProjectReturns one Consent Kit project by its ID.
Action
Get StudyReturns one Consent Kit study by its ID.
Action
List ConsentsReturns a page of consents in your Consent Kit organisation, optionally only agreed or only refused ones.
Action
List Data LinksReturns a page of the data links in your Consent Kit organisation.
Action
List FieldsReturns the custom field definitions configured for your Consent Kit organisation, used to read panellist properties.
Action
List Panel PanellistsReturns the opted-in panellists of a Consent Kit panel, optionally with their email, name and custom field values.
Action
List PanelsReturns a page of your organisation's Consent Kit panels.
Action
List ParticipantsReturns a page of your organisation's Consent Kit participants, optionally with their email and first name.
Action
List ProjectsReturns a page of your organisation's Consent Kit projects, newest first.
Action
List StudiesReturns a page of your organisation's Consent Kit studies.
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.
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 Consent Kit
Consent Kit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Consent Kit to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Consent Kit to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Consent Kit to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Consent Kit to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Consent Kit to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into inMobile - SMS gateway
HubSpot to inMobile - SMS gatewayHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to inMobile - SMS gatewayGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to inMobile - SMS gatewayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to inMobile - SMS gatewayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to inMobile - SMS gatewayGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to inMobile - SMS gatewayActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Consent Kit and inMobile - SMS gateway, answered
What can start an automation from Consent Kit?
Any of Consent Kit's 6 triggers in the catalog, including Consent Updated, New Consent, Participant Created and Consent Agreed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in inMobile - SMS gateway when something happens in Consent Kit?
Any of inMobile - SMS gateway's 15 actions, including Create or Update Contact, Send email, Send RCS text message and Send SMS Message. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from inMobile - SMS gateway to Consent Kit?
Yes. When something happens in inMobile - SMS gateway, your agent can act in Consent Kit too. This page covers both directions: inMobile - SMS gateway's triggers and Consent Kit's actions are listed here as well.
Do I have to build a connector for Consent Kit or inMobile - SMS gateway?
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 Consent Kit and inMobile - SMS gateway 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.