Integration
Connect Nimbata to Leexi
When New form submission fires in Nimbata, your agent runs Add meeting event in Leexi. 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 Nimbata and Leexi 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)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 Nimbata can start in Leexi
When New form submission in Nimbata
then Add meeting event in Leexi
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 Nimbata and Leexi
Triggers and actions 1 trigger · 30 actions
- New form submission
Triggers when a new form submission is received in a Nimbata project.
- Add tag
Creates a new tag in a tag category of a Nimbata project, ready to be applied to calls and form submissions.
- Add tags to call
Adds 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.
- Get call
Returns an inbound call's details, including its attribution, call-flow information and custom field values.
- Get lead
Returns one lead with its phone numbers, emails, and first and last interaction details. If the lead was merged into another, returns the surviving lead.
- Get tracking number
Returns 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.
- List calls
Returns the inbound and outbound calls of a project, newest first, optionally narrowed by date range, caller, tracking number, outcome or campaign.
- List form submissions
Returns the form submissions recorded in a Nimbata project, optionally narrowed by form, date range, attribution, device, tag or value.
- List leads
Returns the identified leads in a Nimbata project, most recent interaction first, optionally narrowed to one phone number or email address.
- List SMS messages
Returns a project's SMS messages, newest first, optionally filtered by date range, direction, status or phone number.
- List tracking numbers
Returns the tracking numbers in a Nimbata project, optionally narrowed by a name or phone number search.
- Add meeting event
Create a meeting event (schedule a meeting to be recorded).
- Add team
Create a team in your Leexi workspace.
- Add user
Creates a user in your Leexi workspace. Requires the write_users permission scope on the API key.
- Delete meeting event
Deletes a Leexi meeting event. Requires the write_meeting_events permission scope on the API key.
- Delete team
Delete a team of the workspace.
- Delete user
Deactivates a Leexi user. Leexi never permanently deletes users: their calls and history are kept, sessions are revoked and they stop consuming a license. Deactivating an already inactive user still succeeds.
- Get call
Get a single Leexi call or meeting, including its topics, AI summary prompts, tasks and transcript.
- Get call note
Retrieve a single call note.
- Get meeting event
Retrieve a single meeting event.
- Get team
Retrieve a single team of the workspace.
- Get user
Retrieve a single user of the workspace.
- Launch meeting assistant
Sends the Leexi meeting assistant (bot) into a meeting event, or stops the bot that is already running.
- List call notes
List call notes for a given call.
- List calls
List the calls and meetings the API key can access, newest first by default, with optional filters on date, source, owner, participants, conversation type and customer contact.
- List teams
List all teams in your Leexi workspace.
- List users
List all users in your Leexi workspace.
- Request presigned recording upload URL
Requests a presigned URL for uploading a call recording before creating the call with Add call. Requires the write_calls permission scope on the API key.
- Update call note
Updates the translated text of a call note for one language. The original note text is not modified. Requires the write_calls permission on the API key.
- Update team
Update the name or active status of a team in your Leexi workspace. Only the values you fill in are changed.
- Update user
Updates a Leexi user. Only the fields you fill in are changed.
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 Nimbata
Nimbata to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Nimbata to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Nimbata to StripeStripe is a payment processing platform for online businesses.
Nimbata to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Nimbata to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Nimbata to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Leexi
HubSpot to LeexiHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LeexiGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LeexiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeexiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Leexi, answered
What can start an automation from Nimbata?
Any of Nimbata's 1 trigger in the catalog, including New form submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leexi when something happens in Nimbata?
Any of Leexi's 20 actions, including Update call note, Update team, Update user and Add meeting event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leexi to Nimbata?
Leexi has no triggers in the catalog today, so automations start in Nimbata. If you need the other direction, ask: your agent reads Leexi's API documentation and adds it.
Do I have to build a connector for Nimbata or Leexi?
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 Nimbata and Leexi 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.