Integration
Connect Zylvie to Buildfire
When New Sale fires in Zylvie, 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 Zylvie 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 Zylvie can start in Buildfire
When New Sale in Zylvie
then Update CMS record in Buildfire
When New Subscription in Zylvie
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 Zylvie and Buildfire
Triggers and actions 3 triggers · 29 actions
Trigger
New SaleTriggers when a new paid sale appears in your Zylvie store.
Trigger
New SubscriptionTriggers when a buyer starts a new subscription.
Trigger
Subscription CancellationTriggers when a subscription is canceled.
Action
Create CouponCreates a coupon code for your Zylvie store.
Action
Create Flash SaleCreates a flash sale that discounts selected products automatically at checkout.
Action
Delete CouponDeletes a coupon, or archives it when it was used in paid sales.
Action
Delete Flash SaleDeletes a flash sale.
Action
Delete ProductDeletes a Zylvie product, or archives it when it has paid sales or active subscriptions.
Action
Get Coupon GrantReturns a customer's coupon grant and when it expires.
Action
Grant Coupon to EmailStarts a customer's redemption window for a shared coupon code.
Action
List CouponsReturns the coupons in your Zylvie store.
Action
List Flash SalesReturns your flash sales, optionally filtered by live state or schedule.
Action
List License CodesReturns a product's uploaded license codes, split into unused and assigned.
Action
List SubscriptionsReturns your store's subscriptions, newest first, with filters for status, subscriber, product and dates.
Action
List TransactionsReturns your store's transactions, newest first, with filters for status, buyer, product and dates.
Action
Redeem License KeyMarks a buyer's license key as redeemed.
Action
Refund License KeyMarks a buyer's license key as refunded so it no longer verifies.
Action
Update CouponUpdates the fields you supply on an existing coupon.
Action
Update Flash SaleUpdates the fields you supply on an existing flash sale.
Action
Update ProductUpdates the fields you supply on an existing Zylvie product.
Action
Verify License KeyChecks that a buyer's license key is valid and paid for the given product.
Action
Verify SubscriptionReturns the subscriptions held by a subscriber's email and their status.
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 Zylvie
Zylvie to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Zylvie to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Zylvie to AnthropicAnthropic builds Claude, a family of large language models.
Zylvie to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Zylvie to ElevenLabsElevenLabs is an AI audio research and deployment company.
Zylvie to PushoverPushover sends real-time push notifications to your phone, tablet, desktop, and watch.
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
Zylvie and Buildfire, answered
What can start an automation from Zylvie?
Any of Zylvie's 3 triggers in the catalog, including New Sale, New Subscription and Subscription Cancellation. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Buildfire when something happens in Zylvie?
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 Zylvie?
Buildfire has no triggers in the catalog today, so automations start in Zylvie. 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 Zylvie 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 Zylvie 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.