Integration
Connect Whippy to Buildfire
When Channels fires in Whippy, your agent runs Update CMS record in Buildfire. 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 Whippy and Buildfire 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 Whippy can start in Buildfire
When Channels in Whippy
then Update CMS record in Buildfire
When List Agents in Whippy
then Insert CMS Record in Buildfire
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 Whippy and Buildfire
Triggers and actions 4 triggers · 30 actions
Trigger
ChannelsTriggers when a new channel is added to your Whippy organization.
Trigger
List AgentsTriggers when a new AI agent is added to your Whippy organization.
Trigger
List CallsTriggers when a new call is logged in Whippy.
Trigger
List UsersTriggers when a new user is added to your Whippy organization.
Action
Add Contacts to a SequenceAdds contacts to a Whippy sequence, creating any contact that does not exist yet.
Action
Create a ContactCreates a new contact in Whippy from a phone number, with optional name, email and opt-in preferences.
Action
Delete a ContactDeletes a contact from Whippy by its ID.
Action
Get Agent by IDReturns one Whippy AI agent by its ID, including its current version and settings.
Action
Get All CampaignsReturns the campaigns in your Whippy organization, optionally filtered by title.
Action
Get All ChannelsReturns the channels (phone numbers, email addresses and other locations) in your Whippy organization.
Action
Get All ContactsReturns the contacts in your Whippy organization, optionally filtered by name, email or phone.
Action
Get All SequencesReturns the sequences in your Whippy organization, optionally filtered by title.
Action
Get All Sequence StepsReturns all the steps of a Whippy sequence, including each step's message and delivery stats.
Action
Get Call by IDReturns one Whippy call by its ID, including its recording and transcript links.
Action
Get Campaign by IDReturns one Whippy campaign by its ID.
Action
Get Campaign ContactsReturns the contacts a Whippy campaign was sent to, with optional filters for delivery, responses, unsubscribes and link clicks.
Action
Get Contact by IDReturns one Whippy contact by its ID.
Action
Get Contacts in a SequenceReturns the contacts enrolled in a Whippy sequence, with optional filters for status, step, responses, unsubscribes and link clicks.
Action
Get Sequence by IDReturns one Whippy sequence by its ID.
Action
List AgentsReturns the AI agents in your Whippy organization, optionally filtered by name.
Action
List CallsReturns calls in your Whippy organization, optionally limited to a date range.
Action
List UsersReturns the users in your Whippy organization, optionally filtered by name, email, phone, role or state.
Action
Send an SMSSends an SMS text message from one of your Whippy channels to a phone number.
Action
Update a ContactUpdates an existing Whippy contact's details such as name, email, phone or opt-in preferences.
Action
Assign Tags to UserAdds one or more tags to a Buildfire app user.
Action
Delete CMS recordDeletes a record from a BuildFire plugin's CMS data by its key.
Action
Delete userRemoves a user from your BuildFire app by username.
Action
Find CMS recordsFinds CMS (plugin data) records in a Buildfire plugin instance by tag, optionally within a date range.
Action
Get User by Access TokenReturns the Buildfire app user that a login access token belongs to, including name, email and activity dates.
Action
Insert CMS RecordAdds a data record to a plugin instance's CMS data under a tag.
Action
Register UserRegisters a new user in a Buildfire app with their email and optional password and name.
Action
Remove tags from userRemoves one or more tags from a BuildFire app user.
Action
Schedule Push NotificationSchedules a push notification to the app's users, to one group, or to users with given tags.
Action
Update CMS recordUpdates (saves) a record in a BuildFire plugin's CMS data collection.
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 Whippy
Whippy to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Whippy to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Whippy to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Whippy to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Whippy to AnthropicAnthropic builds Claude, a family of large language models.
Whippy to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
More into Buildfire
HubSpot to BuildfireHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BuildfireSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BuildfireSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BuildfireGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to BuildfireGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BuildfireGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Whippy and Buildfire, answered
What can start an automation from Whippy?
Any of Whippy's 4 triggers in the catalog, including Channels, List Agents, List Calls and List Users. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Buildfire when something happens in Whippy?
Any of Buildfire's 10 actions, including Update CMS record, Assign Tags to User, Find CMS records and Get User by Access Token. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Buildfire to Whippy?
Buildfire has no triggers in the catalog today, so automations start in Whippy. If you need the other direction, ask: your agent reads Buildfire's API documentation and adds it.
Do I have to build a connector for Whippy or Buildfire?
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 Whippy and Buildfire 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.