Integration
Connect Coro and SerwerSMS
When New Audit Log Entry fires in Coro, your agent runs Add Contact in SerwerSMS, or New Contact in SerwerSMS to Add Ticket Comment in Coro. 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 Coro and SerwerSMS 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 Coro and SerwerSMS can do together
From Coro to SerwerSMS
When New Audit Log Entry in Coro
then Add Contact in SerwerSMS
When New Device in Coro
then Update Contact in SerwerSMS
From SerwerSMS to Coro
When New Contact in SerwerSMS
then Add Ticket Comment in Coro
When New Message in SerwerSMS
then Perform Ticket Action in Coro
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 Coro and SerwerSMS
Triggers and actions 6 triggers · 32 actions
Trigger
New Audit Log EntryTriggers when a new audit log entry is recorded in the workspace.
Trigger
New DeviceTriggers when a new device is enrolled in the workspace.
Trigger
New Protected UserTriggers when a new user appears in the workspace.
Trigger
New TicketTriggers when a new security ticket is created in the workspace.
Action
Add Portal UserInvites a user to the Coro end-user portal.
Action
Add Ticket CommentAdds a comment to a security ticket.
Action
Get Portal UserReturns one end-user portal user by ID.
Action
Get TicketReturns one security ticket by ID.
Action
Get UserReturns one user by ID.
Action
Get WorkspaceReturns the details of the connected Coro workspace.
Action
List DevicesReturns the protected devices in the workspace.
Action
List Portal UsersReturns the users of the Coro end-user portal.
Action
List Ticket ActionsReturns the actions that can be taken on a security ticket.
Action
List Ticket CommentsReturns the comments on a security ticket.
Action
List TicketsReturns security tickets in the workspace, optionally filtered by processed state and time range.
Action
List UsersReturns the users in the workspace, optionally filtered by email or name.
Action
Perform Ticket ActionRuns an action on a security ticket, such as marking it processed.
Action
Search Audit LogsReturns audit log entries for the workspace within an optional time range.
Action
Search WorkspacesReturns the child workspaces the connected workspace can access, optionally filtered by a search term.
Action
Update User ProtectionTurns Coro protection on or off for a user, identified by email.
Trigger
New ContactTriggers when a new contact is added to the SerwerSMS address book.
Trigger
New MessageTriggers when a new incoming SMS or MMS (reply, ND or NDI message) arrives on the account.
Action
Add Blacklisted Phone NumberAdds a phone number to the blacklist so it receives no messages.
Action
Add ContactAdds a contact to a group and returns the new contact's ID.
Action
Add Sender NameSubmits a new alphanumeric sender name (up to 11 characters) for SerwerSMS approval.
Action
Check Blacklisted Phone NumberChecks whether a phone number is on the blacklist.
Action
Create GroupCreates a contact group and returns its ID.
Action
Delete ContactDeletes a contact.
Action
Delete GroupDeletes a contact group, optionally deleting its contacts too.
Action
Get Account LimitsReturns the account type and how many messages of each type (ECO, FULL, MMS, voice, lookup) are left.
Action
List ContactsLists contacts, optionally only those in one group or matching a search phrase.
Action
List Delivery ReportsLists delivery reports of sent messages, filtered by phone number, message ID, status or date range.
Action
List GroupsLists contact groups with their IDs and contact counts, optionally filtered by name.
Action
List Sender NamesLists the account's sender names and whether each is approved, pending or rejected.
Action
Remove Blacklisted Phone NumberRemoves a phone number from the blacklist.
Action
Send SMSSends an SMS with the same text to one phone number. Returns the queued count and the message ID.
Action
Update ContactUpdates an existing contact's details and group.
Action
Update GroupRenames an existing contact group.
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 Coro
Coro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coro to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into SerwerSMS
HubSpot to SerwerSMSHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SerwerSMSSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SerwerSMSGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SerwerSMSGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SerwerSMSGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SerwerSMSGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Coro and SerwerSMS, answered
What can start an automation from Coro?
Any of Coro's 4 triggers in the catalog, including New Audit Log Entry, New Device, New Protected User and New Ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SerwerSMS when something happens in Coro?
Any of SerwerSMS's 16 actions, including Create Group, Send SMS, Update Contact and Update Group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SerwerSMS to Coro?
Yes. When something happens in SerwerSMS, your agent can act in Coro too. This page covers both directions: SerwerSMS's triggers and Coro's actions are listed here as well.
Do I have to build a connector for Coro or SerwerSMS?
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 Coro and SerwerSMS 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.