Integration
Connect Wodify Core to Buildfire
When New/Updated Client fires in Wodify Core, 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 Wodify Core 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 Wodify Core can start in Buildfire
When New/Updated Client in Wodify Core
then Update CMS record in Buildfire
When New/Updated Lead in Wodify Core
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 Wodify Core and Buildfire
Triggers and actions 5 triggers · 31 actions
Trigger
Client Sign InTriggers when a client signs into a class, returning the sign-in with its client, class, program, location and membership details.
Trigger
New/Updated ClientTriggers when a client is added or an existing client is updated in Wodify.
Trigger
New/Updated LeadTriggers when a lead is created or updated in Wodify.
Trigger
Tag Changed on ClientTriggers when a client's tags change (a tag is added to or removed from a client).
Trigger
Tag Changed on LeadTriggers when a lead's tags change (a tag is added or removed), checking the most recently updated leads.
Action
Add classCreates a new one-off class on the Wodify schedule for a program and location, and returns the created class.
Action
Add class reservationReserves a spot in a class for a client, optionally as a recurring reservation.
Action
Add membershipCreates a new membership for a client from a membership template. Values you leave blank are filled in from the template.
Action
Add Tag to ClientAdds one or more tags to a Wodify client and returns the client's current tags.
Action
Add Tag to LeadAdds one or more tags to a Wodify lead and returns the lead's current tags.
Action
Add/Update ClientCreates a new Wodify client, or updates an existing client when a Client ID is supplied. Fields left blank are not changed.
Action
Add/Update LeadCreates a new lead in Wodify, or updates an existing lead when a Lead ID is supplied.
Action
Convert lead to clientConverts a Lead into a Client. Any details you leave blank keep the Lead's existing values.
Action
Delete clientDeletes an inactive Wodify client by its ID.
Action
Delete leadDeletes a lead record from Wodify by its ID.
Action
Find leads by criteriaSearches your Wodify leads with a search query and returns the matching leads.
Action
Get ClientReturns a Wodify client record by its id, including contact details, status, tags, memberships flags and custom field answers.
Action
Get LeadReturns a single Wodify lead record by its lead ID.
Action
Get membershipReturns a single membership record by its membership ID.
Action
List clientsReturns the clients in your Wodify account.
Action
List employeesReturns the employees (staff and coaches) in your Wodify account.
Action
List invoicesReturns the invoices in your Wodify gym, with amounts, status, due and paid dates, and the client or lead each one belongs to.
Action
List leadsReturns the leads in your Wodify account, up to 100 at a time.
Action
List membershipsReturns the memberships in your Wodify account, up to 100 at a time.
Action
Remove Tag From ClientRemoves one or more tags from a Wodify client and returns the client's remaining tags.
Action
Remove Tag From LeadRemoves the given tags from a Wodify lead and returns the lead's remaining tags.
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 Wodify Core
Wodify Core to SoundeeSoundee is a social music marketplace where artists and producers can connect and license music.
Wodify Core to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wodify Core to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Wodify Core to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Wodify Core to AnthropicAnthropic builds Claude, a family of large language models.
Wodify Core 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
Wodify Core and Buildfire, answered
What can start an automation from Wodify Core?
Any of Wodify Core's 5 triggers in the catalog, including New/Updated Client, New/Updated Lead, Tag Changed on Client and Tag Changed on Lead. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Buildfire when something happens in Wodify Core?
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 Wodify Core?
Buildfire has no triggers in the catalog today, so automations start in Wodify Core. 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 Wodify Core 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 Wodify Core 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.