Integration
Connect Nimbata and Whippy
When New form submission fires in Nimbata, your agent runs Add Contacts to a Sequence in Whippy, or Channels in Whippy to Get lead in Nimbata. 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 Whippy 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 Nimbata and Whippy can do together
From Nimbata to Whippy
When New form submission in Nimbata
then Add Contacts to a Sequence in Whippy
From Whippy to Nimbata
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 Whippy
Triggers and actions 5 triggers · 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.
- Channels
Triggers when a new channel is added to your Whippy organization.
- List Agents
Triggers when a new AI agent is added to your Whippy organization.
- List Calls
Triggers when a new call is logged in Whippy.
- List Users
Triggers when a new user is added to your Whippy organization.
- Add Contacts to a Sequence
Adds contacts to a Whippy sequence, creating any contact that does not exist yet.
- Create a Contact
Creates a new contact in Whippy from a phone number, with optional name, email and opt-in preferences.
- Delete a Contact
Deletes a contact from Whippy by its ID.
- Get Agent by ID
Returns one Whippy AI agent by its ID, including its current version and settings.
- Get All Campaigns
Returns the campaigns in your Whippy organization, optionally filtered by title.
- Get All Channels
Returns the channels (phone numbers, email addresses and other locations) in your Whippy organization.
- Get All Contacts
Returns the contacts in your Whippy organization, optionally filtered by name, email or phone.
- Get All Sequences
Returns the sequences in your Whippy organization, optionally filtered by title.
- Get All Sequence Steps
Returns all the steps of a Whippy sequence, including each step's message and delivery stats.
- Get Call by ID
Returns one Whippy call by its ID, including its recording and transcript links.
- Get Campaign by ID
Returns one Whippy campaign by its ID.
- Get Campaign Contacts
Returns the contacts a Whippy campaign was sent to, with optional filters for delivery, responses, unsubscribes and link clicks.
- Get Contact by ID
Returns one Whippy contact by its ID.
- Get Contacts in a Sequence
Returns the contacts enrolled in a Whippy sequence, with optional filters for status, step, responses, unsubscribes and link clicks.
- Get Sequence by ID
Returns one Whippy sequence by its ID.
- List Agents
Returns the AI agents in your Whippy organization, optionally filtered by name.
- List Calls
Returns calls in your Whippy organization, optionally limited to a date range.
- List Users
Returns the users in your Whippy organization, optionally filtered by name, email, phone, role or state.
- Send an SMS
Sends an SMS text message from one of your Whippy channels to a phone number.
- Update a Contact
Updates an existing Whippy contact's details such as name, email, phone or opt-in preferences.
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 Whippy
HubSpot to WhippyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to WhippyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to WhippyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WhippyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Whippy, 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 Whippy when something happens in Nimbata?
Any of Whippy's 20 actions, including Create a Contact, Send an SMS, Update a Contact and Add Contacts to a Sequence. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Whippy to Nimbata?
Yes. When something happens in Whippy, your agent can act in Nimbata too. This page covers both directions: Whippy's triggers and Nimbata's actions are listed here as well.
Do I have to build a connector for Nimbata or Whippy?
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 Whippy 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.