Integration
Connect Keplars and Nimbata
When New Audience fires in Keplars, your agent runs Get lead in Nimbata, or New form submission in Nimbata to Add Contact to Audience in Keplars. 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 Keplars and Nimbata 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 Keplars and Nimbata can do together
From Keplars to Nimbata
When New Audience in Keplars
then Get lead in Nimbata
When New Contact in Audience in Keplars
then List leads in Nimbata
From Nimbata to Keplars
When New form submission in Nimbata
then Add Contact to Audience in Keplars
When New form submission in Nimbata
then Send Email in Keplars
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 Keplars and Nimbata
Triggers and actions 3 triggers · 30 actions
Trigger
New AudienceTriggers when a new audience is created.
Trigger
New Contact in AudienceTriggers when a contact is added to an audience.
Action
Add Contact to AudienceAdds a contact to an audience, reusing an existing contact with the same email.
Action
Add DomainAdds a sending domain and returns the DNS records to publish.
Action
Create AudienceCreates a new audience (contact list).
Action
Delete AudienceDeletes an audience.
Action
Delete ContactDeletes a contact.
Action
Delete DomainDeletes a sending domain.
Action
Enroll Contact in AutomationEnrolls a contact, by email, in a Keplars automation.
Action
Get AudienceReturns one audience by its ID.
Action
Get AutomationReturns one automation by its ID.
Action
Get ContactReturns one contact, looked up by ID or email.
Action
List AudiencesReturns the workspace's audiences.
Action
List AutomationsReturns the workspace's automations.
Action
List Contacts in AudienceReturns the contacts in an audience.
Action
List DomainsReturns the workspace's sending domains.
Action
Remove Contact from AutomationRemoves a contact, by email, from a Keplars automation.
Action
Schedule EmailSchedules a transactional email to be sent at a future date and time.
Action
Send EmailQueues a transactional email for delivery through Keplars.
Action
Track EventRecords a custom event for a contact, which can start event-triggered Keplars automations.
Action
Update ContactUpdates a contact's details.
Action
Verify DomainChecks a sending domain's DNS records and returns its verification result.
Trigger
New form submissionTriggers when a new form submission is received in a Nimbata project.
Action
Add tagCreates a new tag in a tag category of a Nimbata project, ready to be applied to calls and form submissions.
Action
Add tags to callAdds one or more tags to a call and keeps the tags it already has. Returns the call's full list of tag IDs after the change.
Action
Get callReturns an inbound call's details, including its attribution, call-flow information and custom field values.
Action
Get leadReturns one lead with its phone numbers, emails, and first and last interaction details. If the lead was merged into another, returns the surviving lead.
Action
Get tracking numberReturns one tracking number from a project, looked up by its ID or phone number, including its status, line type, country, call flow and tracking source.
Action
List callsReturns the inbound and outbound calls of a project, newest first, optionally narrowed by date range, caller, tracking number, outcome or campaign.
Action
List form submissionsReturns the form submissions recorded in a Nimbata project, optionally narrowed by form, date range, attribution, device, tag or value.
Action
List leadsReturns the identified leads in a Nimbata project, most recent interaction first, optionally narrowed to one phone number or email address.
Action
List SMS messagesReturns a project's SMS messages, newest first, optionally filtered by date range, direction, status or phone number.
Action
List tracking numbersReturns the tracking numbers in a Nimbata project, optionally narrowed by a name or phone number search.
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 Keplars
Keplars to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Keplars to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Keplars to MailchimpMailchimp marketing automation and email platform.
Keplars to StripeStripe is a payment processing platform for online businesses.
Keplars to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Keplars to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Nimbata
HubSpot to NimbataHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to NimbataGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to NimbataGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NimbataGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to NimbataGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to NimbataMailchimp marketing automation and email platform.
Questions
Keplars and Nimbata, answered
What can start an automation from Keplars?
Any of Keplars's 2 triggers in the catalog, including New Audience and New Contact in Audience. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Nimbata when something happens in Keplars?
Any of Nimbata's 10 actions, including Add tag, Add tags to call, Get call and Get lead. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Nimbata to Keplars?
Yes. When something happens in Nimbata, your agent can act in Keplars too. This page covers both directions: Nimbata's triggers and Keplars's actions are listed here as well.
Do I have to build a connector for Keplars or Nimbata?
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 Keplars and Nimbata 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.