Overview
Zapier lets you connect third-party tools (like forms, CRMs, or reporting systems) to your Buildfire app. This means you can automate tasks like banning or removing a user if they violate your rules, cancel a subscription, or trigger a flag in your system.
Removing a user deletes their profile from the User Management tab, and they won’t be able to log in again with the same email address. Banning a user keeps their information in the system but prevents them from using the app until they are unbanned.
Required
Growth or Scale plan.
You must request a Zapier API key and invitation link from Buildfire Support.
Your data source must include the user's email address.
How to ban a user using Zapier
Contact Buildfire Support to request:
A Zapier invitation link.
Your app’s Zapier API key.
Accept the invitation and connect your Buildfire app to Zapier.
In Zapier, click Create Zap.
Choose a Trigger app (e.g., Typeform, Google Sheets, Webflow).
Set the trigger event (e.g., form submission, column update).
Click Continue and then Test Trigger to verify incoming data.
Add an Action step:
Choose Buildfire as the app.
Set the Action Event to Remove or Ban User.
Under Account, select your connected Buildfire account (or enter your API key).
Click Continue.
Map the Email field to the user email coming from your trigger app.
Select if you want to Remove or Banned.
Click Continue, then Test Step to confirm the action.
Click Publish to activate the Zap.
Pro tips
Ban user Zaps are useful for abuse reporting systems or subscription cancellations.
Combine with tagging or logging actions for better audit control.
Troubleshooting tips
Zap not working? Double-check the API key and make sure the trigger app is correctly passing the email.
Is the user still active? Make sure the email exists in your Buildfire app and matches exactly.