Integration
Connect Blink to Buildfire
When New Form Submission fires in Blink, 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 Blink 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 Blink can start in Buildfire
When New Form Submission in Blink
then Update CMS record in Buildfire
When New Form Submission in Blink
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 Blink and Buildfire
Triggers and actions 1 trigger · 18 actions
Trigger
New Form SubmissionTriggers when someone submits the chosen Blink form.
Action
Archive Feed PostDismisses a feed post for everyone who received it.
Action
Archive Feed Post for UserDismisses a feed post for one user who received it.
Action
Find Feed Post by External IDFinds a feed post's ID from the external ID it was sent with.
Action
Find UsersReturns users in your Blink organisation, optionally filtered by email, employee ID or user ID.
Action
List Feed CategoriesReturns the feed categories defined for your Blink integration.
Action
List FormsReturns the forms in your Blink organisation.
Action
Post to FeedPosts a new card to the feeds of the selected users or teams.
Action
Update Feed PostEdits the card of a feed post that was already sent.
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 Blink
Blink to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Blink to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Blink to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Blink to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Blink to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Blink to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Blink and Buildfire, answered
What can start an automation from Blink?
Any of Blink'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 Buildfire when something happens in Blink?
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 Blink?
Buildfire has no triggers in the catalog today, so automations start in Blink. 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 Blink 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 Blink 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.