Integration
Connect Nimbata to Peaka
When New form submission fires in Nimbata, your agent runs Run Peaka Query (With Line Item Support) in Peaka. 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 Peaka 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 Peaka
When New form submission in Nimbata
then Run Peaka Query (With Line Item Support) in Peaka
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 Peaka
Triggers and actions 1 trigger · 20 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 connection
Creates a new data source connection in a Peaka project.
- Add query
Creates a saved SQL query (plain or materialized) in a Peaka project, optionally inside a folder.
- Delete connection
Deletes a connection from a Peaka project. Any catalogs using this connection lose access to their data source.
- Delete query
Permanently deletes a saved query from a Peaka project.
- Get query
Returns a single saved query in a Peaka project by its ID, including its SQL, type, schedule and folder location.
- List connections
Lists all connections (authenticated links to external data sources) in a Peaka project.
- List projects
Lists all projects within a Peaka workspace.
- List queries
Returns all saved queries in a Peaka project, including each query's folder path when it sits in a folder.
- Run Peaka Query (With Line Item Support)
Runs a SQL statement, a saved query, or a query builder request in a Peaka project and returns the result rows as line items.
- Update query
Updates the display name, SQL, type or schedule of an existing Peaka query. 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 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 Peaka
HubSpot to PeakaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PeakaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PeakaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PeakaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Peaka, 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 Peaka when something happens in Nimbata?
Any of Peaka's 10 actions, including Update query, Add connection, Add query and Get query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Peaka to Nimbata?
Peaka has no triggers in the catalog today, so automations start in Nimbata. If you need the other direction, ask: your agent reads Peaka's API documentation and adds it.
Do I have to build a connector for Nimbata or Peaka?
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 Peaka 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.