Integration
Connect Leadport and Romulus
When New Customer fires in Leadport, your agent runs Create Campaign Call Task in Romulus, or New Call in Romulus to Add task in Leadport. 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 Leadport and Romulus 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 Leadport and Romulus can do together
From Leadport to Romulus
When New Customer in Leadport
then Create Campaign Call Task in Romulus
When New Customer in Leadport
then Create Contact in Romulus
From Romulus to Leadport
When New Call in Romulus
then Add task in Leadport
When New SMS Message in Romulus
then Add ticket in Leadport
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 Leadport and Romulus
Triggers and actions 3 triggers · 45 actions
Trigger
New CustomerTriggers when a new customer is added to your Leadport account.
Action
Add taskCreates a task for a Leadport customer, optionally assigned to a user with a planned date and priority.
Action
Add ticketCreates a new ticket for a customer in Leadport.
Action
Add ticket offerCreates an offer on an existing customer ticket in Leadport, with a name, amount and description.
Action
Add ticket saleRecords a new sale against a customer's ticket in Leadport, with its amount and optional custom template values.
Action
Create GMC (Golden Moment Call) LeadCreates a Golden Moment Call lead in Leadport, which triggers an immediate call between your team and the customer.
Action
Create or Update CustomerCreates a Leadport customer, or updates an existing one when a customer ID is given.
Action
Get CustomerReturns one Leadport customer by its ID.
Action
Get taskReturns a Leadport task with its details, including the customer, assignee, type, planned date and call count.
Action
Get ticketReturns a ticket's details, including its customer, assignee, status and form field values, plus the ticket form template.
Action
List ChannelsReturns the lead channels configured in your Leadport account.
Action
List Customer EventsReturns the activity events (calls, tasks, notes) recorded for a Leadport customer.
Action
List reasonsReturns the reasons configured in your Leadport account, optionally filtered by reason type.
Action
List tasks by customerReturns the tasks belonging to a Leadport customer.
Action
List tickets by customerReturns all tickets belonging to a Leadport customer.
Action
List usersReturns all active users in your Leadport account, with their names, emails and roles.
Action
Search CustomersFinds Leadport customers whose details match a keyword (name, email, phone).
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.
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 Leadport
Leadport to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Leadport to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Leadport to MailchimpMailchimp marketing automation and email platform.
Leadport to StripeStripe is a payment processing platform for online businesses.
Leadport to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Leadport to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Romulus
HubSpot to RomulusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RomulusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to RomulusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RomulusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RomulusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RomulusMailchimp marketing automation and email platform.
Questions
Leadport and Romulus, answered
What can start an automation from Leadport?
Any of Leadport's 1 trigger in the catalog, including New Customer. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Romulus when something happens in Leadport?
Any of Romulus's 29 actions, including Create Campaign Call Task, Create Click-to-Call Configuration, Create Contact and Send SMS. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Romulus to Leadport?
Yes. When something happens in Romulus, your agent can act in Leadport too. This page covers both directions: Romulus's triggers and Leadport's actions are listed here as well.
Do I have to build a connector for Leadport or Romulus?
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 Leadport and Romulus 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.