How to Tag and Untag a User (Using Zapier)

This step-by-step tutorial explains how to tag and untag a user in your BuildFire app using Zapier. For more information on Zapier, what it is, and how it works, check out our Zapier Knowledge Base.

In this tutorial, we’re going to use Google Sheets as the data source. But it’s worth noting that you could easily use another platform. It all depends on where your user data is. For example, you’d be able to follow using the same steps using Shopify, Salesforce, or another platform containing user information.

Before you do anything in Zapier, you need to prepare your spreadsheet ahead of time with the information for user tags. Make sure you label the Google Sheet, worksheet tab, and columns appropriately. This will make things much easier as you continue creating multiple workflows with Zapier.

Here’s a simple spreadsheet template that you can follow for tagging a user:

Pay close attention to the spreadsheet name, worksheet tab name, and column headers mentioned above. We’re going to be looking for this information once we jump into Zapier.

This example is really easy. We’re just saying the email address located in the “Email” column is going to be tagged with the word in the “Tag” column. You can continue adding multiple columns for additional tags if you’d like to do so.

Head over to your Zapier dashboard and click “Make a Zap” at the top left corner of the screen.

If you’re on a free Zapier plan, you can create 5 Zaps and 100 tasks. Beyond that, you’ll need to upgrade to the premium version of this software. Zapier is a third-party tool and completely separate from your BuildFire subscription.

The first thing you need to do is begin your trigger. Since the user tag information is located in Google Sheets, we want to start by selecting the Google Sheets app in Zapier.

If you don’t see the Google Sheets app on the initial menu, just search for it using the search bar at the top of this screen.

Next, find “New or Updated Spreadsheet Row” from the Trigger Event dropdown menu.

If you’re not already signed into Google Sheets from your Zapier account, you’ll be prompted to do so.

Scroll through the Google Sheets associated with your linked account until you find the spreadsheet that was created back in the first step. If you don’t find it by scrolling, you can always search for it by name.

Then select the “Tag Users” tab from the “worksheet value” field within Zapier.

This is telling Zapier to pull the information from that particular spreadsheet with your user tagging data.

Click continue to proceed.

Next, Zapier will find a recent spreadsheet row within that particular Google Sheet and pull the information to test. This will ensure that you have everything set up correctly.

After you’ve verified that the information is correct, click continue to proceed.

Now Zapier is going to ask you to set up another app and event. For this specific purpose, we want to take the data from Google Sheets and send it to BuildFire to tag users within the app.

Assuming you already have the invitation from BuildFire, the app will appear in your Zapier menu.

If you don’t see the icon and you know that you’ve already been invited, just search for “BuildFire” in the search bar, and it should appear.

Click the icon to continue.

Similar to what we did earlier when setting up an event within Google Sheets, we need to do the same for BuildFire. In this case, we’re telling Zapier what we want to do within BuildFire using the data from our spreadsheet.

In this particular case, select “Assign User Tag” from the menu.

Click continue.

Again, now we need to tell the BuildFire app where to pull the information from.

Select the spreadsheet (in this tutorial example, it’s labeled “Zapier Training”). Then select the worksheet tab name, which is “Tag Users” in this example.

Once you’ve filled in the necessary fields, it’s time to test the trigger.

These will look nearly identical to the test we ran earlier in step #6. The only difference for this one is that we’re incorporating the test with BuildFire as the final destination for the spreadsheet data.

Finally, match the “Tags” and “Email” fields in Zapier with the columns from your spreadsheet.

If you have multiple tags, then continue adding to each subsequent field in that section. For simplicity’s sake, it’s probably best to just name the columns in your spreadsheet Tag 1, Tag 2, etc., if you’re going to add more than one.

Click continue.

Finally, just test the Zap. Once you see that the test was successful, click “Turn on Zap” and you’re done.

Now whenever new data is added to that spreadsheet, users will automatically be tagged accordingly in BuildFire.

This step-by-step process is going to be nearly identical to the one above. Since you already have tags in place, this will be much easier to understand.

Just like you did for the initial tag, you need to start with a Google Sheet and label the spreadsheet, worksheet, and columns accordingly.

In this case, we have the columns labeled as “Email” and “Remove Tag.” It will ultimately do the reverse action of adding the tag, which was set up earlier.

Start by clicking “Make a Zap” on your Zapier dashboard.

Just like we did before, select “Google Sheets” as the app and “New or Updated Spreadsheet Row” for the trigger event.

Now just scroll or search for the Google Sheet that contains the untag user data. Then choose the corresponding worksheet title tab.

In this example, the spreadsheet name is “Zapier Training” and “Untag Users” is the name of the worksheet.

Click continue. Then test the trigger to make sure everything works.

Once we’ve connected the data from Google Sheets, we need to tell Zapier where that information is going. Scroll or search for BuildFire from your list of Zapier apps. Then select “Unassign User Tag” from the dropdown menu of event options.

Click continue, and link your BuildFire account to proceed.

Continue mapping your Zap by matching the “Email” field to the “Email” column in your Google Sheet, as well as the “Tag” field to the “Remove Tag” column.

Click continue. Test the Zap.

Make sure the Zap is named appropriately. Then just turn on the Zap, and you’re done.