Integration
Connect Nimbata to Qdrant
When New form submission fires in Nimbata, your agent runs Add collection in Qdrant. 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 Qdrant 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 Qdrant
When New form submission in Nimbata
then Add collection in Qdrant
When New form submission in Nimbata
then Add payload index in Qdrant
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 Qdrant
Triggers and actions 1 trigger · 25 actions
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.
Action
Add collectionCreates a new Qdrant collection with the given name and vector configuration.
Action
Add payload indexCreates a payload index on a field of a Qdrant collection so that filters on that field run fast.
Action
Add pointsAdds points (vectors with optional payloads) to a Qdrant collection, overwriting any existing point with the same id.
Action
Add snapshotCreates a new snapshot of a Qdrant collection and returns the snapshot's name, size and checksum.
Action
Count pointsReturns the number of points in a Qdrant collection, optionally only those matching a payload filter.
Action
Delete collectionDeletes a Qdrant collection and all of the points and data stored in it.
Action
Delete pointsDeletes points from a Qdrant collection, either by a list of point ids or by every point matching a filter.
Action
Find points by vectorReturns the points in a collection whose vectors are closest to the vector you supply, ranked by similarity score, with their payloads.
Action
Get collectionReturns the details of a Qdrant collection: its status, point and vector counts, segment count, configuration and payload index schema.
Action
Get pointReturns a single point from a Qdrant collection, including its payload and vector.
Action
List collectionsReturns the names of all collections in your Qdrant cluster.
Action
List pointsReturns the points stored in a Qdrant collection, optionally narrowed by a payload filter and ordered by a payload field.
Action
List snapshotsReturns every snapshot stored for a Qdrant collection, with each snapshot's file name, creation time, size and checksum.
Action
Update collectionUpdates the settings of an existing Qdrant collection, such as its vector, index, optimizer, quantization, strict-mode or metadata parameters.
Action
Update point payloadSets payload values on points in a Qdrant collection, chosen by point ids or a filter. Keys you supply are added or overwritten; other existing payload keys are kept.
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 Qdrant
HubSpot to QdrantHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to QdrantSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to QdrantSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to QdrantGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to QdrantGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QdrantGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Qdrant, 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 Qdrant when something happens in Nimbata?
Any of Qdrant's 15 actions, including Update collection, Update point payload, Add collection and Add payload index. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qdrant to Nimbata?
Qdrant has no triggers in the catalog today, so automations start in Nimbata. If you need the other direction, ask: your agent reads Qdrant's API documentation and adds it.
Do I have to build a connector for Nimbata or Qdrant?
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 Qdrant 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.