Integration
Connect Romulus to Livestorm
When New Call fires in Romulus, your agent runs Create Event in Livestorm. 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 Romulus and Livestorm 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 Romulus can start in Livestorm
When New Call in Romulus
then Create Event in Livestorm
When New SMS Message in Romulus
then Update Event in Livestorm
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 Romulus and Livestorm
Triggers and actions 2 triggers · 45 actions
Trigger
New CallTriggers when a new call is recorded, optionally only for one AI agent or direction.
Trigger
New SMS MessageTriggers when a new SMS message is sent or received, optionally only one direction.
Action
Create Campaign Call TaskAdds a recipient to a call campaign as a new call task.
Action
Create Click-to-Call ConfigurationCreates a Click-to-Call configuration that connects a contact to an AI agent, extension, DID or DID rule. Give exactly one routing target.
Action
Create ContactCreates a new contact with a phone, email, company and tags.
Action
Delete Click-to-Call ConfigurationPermanently deletes a Click-to-Call configuration.
Action
Delete ContactPermanently deletes a contact with all its phones, emails and addresses.
Action
Get Click-to-Call ConfigurationReturns one Click-to-Call configuration and its routing target.
Action
Get ContactReturns one contact with its phones, emails, addresses and tags.
Action
Get DIDReturns one DID phone number, with its label and status.
Action
Get Outbound Caller IDReturns one outbound caller ID, with its number and verification status.
Action
Initiate Click-to-CallCalls a contact and connects them to the routing target of a Click-to-Call configuration.
Action
List Agent Call TasksReturns the call tasks scheduled for an AI agent, with their status and next attempt time.
Action
List Click-to-Call ConfigurationsReturns your Click-to-Call configurations and their routing targets.
Action
List DID RulesReturns the routing rules of a DID phone number, with their schedules.
Action
List ExtensionsReturns your internal extensions: users, queues, groups, cascades and AI agents.
Action
List Outbound Caller IDsReturns the outbound caller IDs in your organization, optionally filtered by label, number or status.
Action
List SMS SendersReturns the SMS senders configured for your organization, optionally filtered by name or type.
Action
List WhatsApp BotsReturns your WhatsApp bots and the message templates each one can send.
Action
Search CallsReturns calls matching the filters you give, such as agent, direction, status, phone number or date range.
Action
Search ContactsReturns contacts matching the filters you give, such as name, phone, email, company or tag.
Action
Search DIDsReturns the DID phone numbers in your organization, optionally filtered by number, label or status.
Action
Search SMS MessagesReturns SMS messages matching the filters you give, such as sender, recipient, status, direction or date range.
Action
Send SMSSends an SMS from one of your organization's senders to a phone number.
Action
Send WhatsApp Template MessageSends an approved WhatsApp template message from one of your bots to a phone number, filling in the template's variables.
Action
Start Agent Call TaskSchedules a call task so an AI agent calls a contact, retrying if they do not answer.
Action
Terminate Agent Call TaskStops an active agent call task so no further attempts are made.
Action
Terminate Agent Call Tasks by Phone NumberStops every active agent call task for a contact phone number.
Action
Terminate Campaign Call Tasks by Phone NumberStops every call task for a phone number within a campaign.
Action
Update Click-to-Call ConfigurationChanges a Click-to-Call configuration. Only the values you give change; a new routing target replaces the old one.
Action
Update ContactReplaces a contact's details. Romulus clears any field you leave empty, so send every value the contact should keep.
Action
Create EventCreates a new Livestorm event with its first session, either from scratch or by duplicating the settings of an existing event.
Action
Create RegistrantRegisters a person for an upcoming Livestorm event session, with their email, name, registration fields and UTM tracking data.
Action
Create SessionSchedules a new session for an existing Livestorm event. Returns the created session, including its room link, status and scheduled start time.
Action
Find PeopleFinds people in your Livestorm workspace by email address, optionally limited to participants or team members.
Action
Find SessionFinds event sessions in your Livestorm workspace whose name matches the one you give, optionally narrowed by status and date range. Returns the matching sessions and the first match.
Action
Get eventReturns a single Livestorm event, including its title, status, registration link, settings, owner and registration fields.
Action
Get personReturns the details of a person in your Livestorm workspace, such as their name, email, role and timezone.
Action
Get sessionReturns a single Livestorm session, including its status, schedule, room link and attendee counts, optionally with its event, people, chat messages, questions or recordings.
Action
List eventsReturns the events in your Livestorm workspace, optionally filtered by title, scheduling status, tag, or creation and update dates.
Action
List session questionsReturns all the questions attendees asked during a Livestorm session, with any answers given.
Action
List sessionsReturns the sessions across all events in your Livestorm workspace, optionally filtered by status, scheduled start date, creation date or last update date.
Action
Remove EventDeletes a single Livestorm event.
Action
Remove RegistrantRemoves a registrant from a Livestorm event session, cancelling their registration.
Action
Remove SessionDeletes a single Livestorm event session.
Action
Update EventUpdates an existing Livestorm event, changing only the details you fill in, such as its title, description, status or room settings.
Action
Update SessionUpdates a Livestorm session's name, start date/time or timezone. Fields left blank keep their current values.
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 Romulus
Romulus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Romulus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Romulus to StripeStripe is a payment processing platform for online businesses.
Romulus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Romulus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Romulus to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Livestorm
HubSpot to LivestormHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LivestormSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LivestormSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LivestormGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LivestormGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LivestormGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Romulus and Livestorm, answered
What can start an automation from Romulus?
Any of Romulus's 2 triggers in the catalog, including New Call and New SMS Message. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Livestorm when something happens in Romulus?
Any of Livestorm's 16 actions, including Create Event, Create Registrant, Create Session and Update Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Livestorm to Romulus?
Livestorm has no triggers in the catalog today, so automations start in Romulus. If you need the other direction, ask: your agent reads Livestorm's API documentation and adds it.
Do I have to build a connector for Romulus or Livestorm?
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 Romulus and Livestorm 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.