All Collections
Integrations
Zapier
Bulk Assign User Access with Zapier
Bulk Assign User Access with Zapier

Use the native integration with Zapier to bulk assign subscriptions

Diego Quintero avatar
Written by Diego Quintero
Updated over a week ago

Transfer is a brand new beta feature from Zapier that you can use to send bulks of data from one app to another.

Prepare the Data

The first step before assigning the access is to organize the data in a spreadsheet. We will use Google Sheets and create a sheet with two columns (email and name), then we will add a row for each end-user.

Create a Zapier Transfer

To create a Zapier Transfer, you can navigate to the following page and click Continue: https://transfer.zapier.com/new

Select your source and destination apps, the source data, and the destination action. We recommend using Assign User Access.

Proceed to connect your Google Sheets account to access the data.

Select the spreadsheet and worksheet of your data source.

Then, connect your Uscreen account.

Select the data you will import from Google Sheets to assign user access to your Uscreen subscription or bundle in bulk.

Some fields are mandatory:

  • Email

  • Full Name

  • Subscription/Bundle

  • Charge subscriptions outside of Uscreen

Other fields are not mandatory but recommended:

Review the data fields to confirm you mapped the right ones.

Select the records that you want to import. You can filter the records or use the Select All button.

You will see a final confirmation that includes the estimated duration of the data transfer and the tasks count. Click on Send Data.

NOTE: You can send up to 25,000 records per Transfer cycle, but Free and trial accounts can preview up to 100 of the most recent records from their source app. Paid accounts have no limit. You can upgrade your Zapier plan if you want to preview more records or add more tasks to your account.

You can view the progress of your transfer as well.

When the task is completed, the users from the spreadsheet will have the subscription or bundle assigned to them. If the user doesn't exist, the task will create a new account.

Did this answer your question?