Zapier allows you to connect Uscreen with thousands of other applications, creating automated workflows between them.
These connections, called Zaps, consist of a trigger (when this happens...) and one or more actions (...do this as a result).
🔗 Learn more about Key Concepts in Zaps
📝 NOTE: Zapier integration is available for the App Essentials or Plus plan. If you're not currently on these plans, please get in touch with sales@uscreen.tv.
Connect Uscreen to Zapier
In Uscreen
Navigate to Settings > Integrations
Copy your Zapier API Key
In Zapier
Navigate to App Connections
Click Add Connection
Search for and select Uscreen, and click Add Connection
Enter the copied API Key from Uscreen
Click Yes, Continue to Uscreen
📝 NOTE: While we can assist with issues related to the Uscreen side of the Zapier integration, our ability to support general Zapier or third-party app issues is limited. For such, please contact Zapier Support directly.
Create your Zap
In Zapier
Pair your App
Alternatively, you can use the page below to easily pair Uscreen with the app of your choice and view the available zaps that you may create for both apps.
ℹ️ INFO: You may create a series of actions depending on your Zapier plan. You can also use the built-in Copilot (AI) of Zapier for assistance in creating your workflow.
When this happens… (Trigger)
Uscreen offers several triggers that can start your Zap workflow.
Began to Play Video
Fires when a member clicks Play on a video.
Field | Description |
Video Title | The title of the video that was played |
The unique ID of the video in Uscreen | |
Customer Name | The member's full name |
Display Name | The member's display name, if set. If no display name has been set, this will match the Customer Name |
The member's email address | |
The unique ID of the member in Uscreen | |
User Legacy ID | The member's ID from a prior platform, if set during migration. Blank if not applicable |
Chapter ID | The ID of the specific chapter that was played, if the video has chapters. Blank if no chapters exist |
Legacy ID | The video's ID from a prior platform, if set during migration. Blank if not applicable |
Event | Always |
📝 NOTE: This trigger fires when the Play button is clicked. It does not indicate whether the video was watched in full, and it triggers only once per video per user.
Canceled Subscription
Fires when a member's subscription is canceled.
Field | Description |
ID | The unique ID of the ownership (access) record that was canceled |
Name | The member's full name |
Display Name | The member's display name, if set. If no display name has been set, this will match the Name |
The member's email address | |
The unique ID of the member in Uscreen | |
User Legacy ID | The member's ID from a prior platform, if set during migration. Blank if not applicable |
The unique ID of the subscription or bundle that was canceled | |
Offer Title | The name of the subscription or bundle that was canceled |
IP Address | The IP address recorded at the time of the original purchase |
How the member originally purchased the subscription | |
Currency | The currency used for the subscription |
Coupon | The coupon code applied to the original purchase, if any. Blank if no coupon was used |
Transaction ID | The payment processor's transaction ID for the last successful payment. Blank for plans with a free trial where no payment was made |
Event | Always |
ℹ️ INFO: This trigger fires when a subscription is canceled from the member's User Dashboard or when an admin cancels it from the People page. It does not fire if access is revoked using End Membership or due to an overdue invoice.
New User
Fires when a new member account is created on your storefront.
Field | Description |
The unique ID of the new member in Uscreen | |
Name | The member's full name |
Display Name | The member's display name, if set. If no display name has been set, this will match the Name |
The member's email address | |
Any custom user field values collected at signup. Can have multiple nested fields and values depending on the custom fields you've set up | |
How the member's account was created | |
Any tags assigned to the member. Can have multiple values | |
Opted In For News And Updates | Whether the member has opted in to marketing and news emails. Returns |
Opted In For Community Updates | Whether the member has opted in to community notification emails. Returns |
Legacy ID | The member's ID from a prior platform, if set during migration. Blank if not applicable |
UTM Params | A nested group of UTM tracking parameters captured at signup, if available: |
↳ UTM Source | The traffic source (e.g. |
↳ UTM Medium | The marketing medium (e.g. |
↳ UTM Term | The paid search keyword, if applicable |
↳ UTM Content | Used to differentiate ads or links in the same campaign |
↳ UTM Campaign | The name of the campaign (e.g. |
Event | Always |
ℹ️ INFO: This trigger fires when a new member account is created via web checkout, admin invite, landing page email capture, giveaway funnel, or YouTube lead generator. UTM parameter fields will be blank if no UTM tracking was present when the member signed up.
Paid Order
Fires when a payment is processed for a subscription, bundle, or piece of content.
Field | Description |
The unique ID of the invoice generated for the order | |
Offer Title | The name of the subscription, bundle, or content that was purchased |
Total Price | The gross amount before any discount was applied |
Final Price | The net amount after any discount was applied |
Discount | The amount deducted by a coupon, if one was used |
The unique ID of the subscription, bundle, or content that was purchased | |
Name | The member's full name |
Customer Display Name | The member's display name, if set. If no display name has been set, this will match the Name |
The member's email address | |
The unique ID of the member in Uscreen | |
User Legacy ID | The member's ID from a prior platform, if set during migration. Blank if not applicable |
IP Address | The IP address recorded at the time of purchase |
Country Code | The two-letter country code of the purchase location (e.g. |
Transaction ID | The payment processor's transaction ID for the order |
The payment provider or channel through which the order was placed | |
Coupon | The coupon code applied to the order, if any. Blank if no coupon was used |
Event | Always |
💡 TIP: This trigger fires for any invoice marked as Paid, including $0 invoices. If you want to filter out free orders, use a Filter or Paths step in your Zap to check that the Final Price is greater than zero.
User Updated
Fires when a member's account details or subscription status changes.
ℹ️ INFO: The Changes fields contain only the data that was modified. The Attributes fields always contain the member's full current data, regardless of what has changed. Use Changes fields to detect what triggered the event, and Attributes fields to get the member's latest state.
Field | Description |
The unique ID of the member in Uscreen | |
The member's current email address | |
Changes | The full raw object of all modified fields. Only fields that actually changed are included. See individual Changes fields below: |
↳ Changes Email | The member's updated email address, if changed |
↳ Changes Name | The member's updated full name, if changed |
↳ Changes Display Name | The member's updated display name, if changed |
↳ Changes Lifetime Spent | The member's updated total spend, if changed |
↳ Changes Bounced Email | Whether the member's email is bouncing. Returns |
↳ Changes Subscription Status | The member's previous subscription state at the time the change was triggered (e.g. |
↳ Changes Subscription Activity Status | The type of subscription change that occurred (e.g. |
↳ Changes Opted In For News And Updates | Whether the member has opted in to marketing and news emails, if changed. Returns |
↳ Changes Opted In For Community Updates | Whether the member has opted in to community notification emails, if changed. Returns |
Attributes | The full raw object of all current user data, regardless of what changed. See individual Attributes fields below |
↳ Attributes Name | The member's current full name |
↳ Attributes Display Name | The member's current display name, if set. If no display name has been set, this will match the Attributes Name |
↳ Attributes Email | The member's current email address |
↳ Attributes Subscription Status | The member's current subscription state |
↳ Attributes Lifetime Spent | The member's total spend to date |
↳ Attributes Bounced Email | Whether the member's email is currently bouncing. Returns |
↳ Attributes Segments | The member's current segment(s). Can have multiple values |
↳ Attributes Status | The member's current subscription activity status |
↳ Attributes Origin | How the member's account was originally created |
↳ Attributes Tags | Any tags currently assigned to the member. Can have multiple values |
↳ Attributes Opted In For News And Updates | Whether the member is currently opted in to marketing and news emails. Returns |
↳ Attributes Opted In For Community Updates | Whether the member is currently opted in to community notification emails. Returns |
↳ Attributes Legacy ID | The member's ID from a prior platform, if set during migration. Blank if not applicable |
Event | Always |
ℹ️ INFO: This trigger now also fires when a member updates their Display Name. Changes to member Tags and Segments are captured in the Attributes fields, but may not always appear in the Changes fields. Also, this trigger fires when an admin deletes a member's account.
Mapped Fields Values
Origin
The origin field means different things depending on which trigger it appears in.
Here's a breakdown by context:
User Origin
Appears in: New User, User Updated (Attributes Origin). Describes how the member's account was originally created.
Value | Description |
| Signed up via your website |
| Signed up via your mobile or TV app |
| Signed up using Google |
| Signed up using Apple |
| Invited individually by an admin |
| Added via bulk invite by an admin |
| Joined via a team subscription invite |
| Joined via a group subscription invite link |
| Created via Zapier |
| Created via the Publisher API |
| Imported via data migration |
| Joined via gift card redemption |
| Joined via a donation |
| Account created through an abandoned checkout flow |
| Registered for a live event before having an account |
Ownership Origin
Appears in: Canceled Subscription. Describes how the member originally gained access to the subscription or offer.
Value | Description |
| Member purchased directly |
| Admin manually assigned access |
| Access granted via Zapier |
| Access granted via the Publisher API |
| Access imported via data migration |
| Access granted via gift card |
| Access granted via donation |
| Access via a group subscription |
| Access via a group subscription invite link |
| Mobile External Purchase via iOS app |
| Mobile External Purchase via Android app |
| Mobile External Purchase (legacy, for older records only) |
Payment Provider Origin
Appears in: Paid Order. Describes the payment provider used for the transaction.
Value | Description |
| Paid via Stripe (most common) |
| Paid via PayPal (legacy) |
| Paid via native PayPal integration |
| Paid via Amazon Appstore |
| Paid via Google Play Store |
| Paid via Apple App Store |
| Paid via Authorize.Net |
| Paid via Braintree |
| Paid via Roku Channel Store |
| Internal Uscreen transaction |
| No payment provider recorded (legacy records only) |
Segment
Appears in: User Updated (Attributes Segments). A member can belong to multiple segments simultaneously.
Value | Description |
| Has an active subscription |
| Currently in a free trial period |
| Purchased a one-time offer (content or bundle) |
| Subscription is currently paused |
| Had a subscription but no longer active |
| Signed up but has not yet purchased |
| Provided their email only, with no purchase or account |
Subscription Status (legacy)
Appears in: User Updated (Changes Subscription Status, Attributes Subscription Status). This is a legacy field retained for backward compatibility. It reflects the member's overall subscription state.
Value | Description |
| Has never had a subscription |
| Currently in a free trial |
| Active, paid subscription |
| Subscription on hold due to unpaid invoices |
| Previously had a subscription, no longer active |
| Subscription is currently paused |
📝 NOTE: This is an older field that Uscreen has retained for backward compatibility. Some values like pending_cancellation and pending_pausing have been removed from this field, as they now appear in the Subscription Activity Status field instead. If you're building new Zaps, we recommend using Subscription Activity Status for more accurate subscription change tracking.
Subscription Activity Status (new)
Appears in: User Updated (Changes Subscription Activity Status, Attributes Status). Describes the type of subscription change that just occurred, rather than the member's overall state. This field is transient, and it reflects a recent change, not a permanent status.
Value | Description |
| First-time subscriber who just started paying or converted from a trial |
| Former subscriber who has reactivated their subscription |
| Moved to a higher-priced plan or longer billing period |
| Moved to a lower-priced plan or shorter billing period |
| Subscription scheduled to cancel at the end of the current period |
| Subscription scheduled to pause at the end of the current period |
| Subscription is on hold due to unpaid invoices |
| Subscription is currently paused |
ℹ️ INFO: The Attributes Status field in the User Updated trigger maps to the same values as Subscription Activity Status. Both fields are kept for compatibility, where Subscription Activity Status is the current standard.
...do this (Actions)
Uscreen provides two actions that can be performed when triggered by other apps.
Create User
Creates a new member account in your Uscreen store with the required information.
ℹ️ INFO: When successful, the new member account will immediately appear in your People page. New members created via Zapier are automatically opted in to marketing and news emails.
Assign User Access
Adds a subscription or bundle to an existing member account.
📝 NOTE: Select True in Charge subscriptions outside of Uscreen if you are manually billing your members outside of Uscreen. When set to True, subscription access is granted, but free trials are not applied. When set to False, both subscription access and free trials are granted. Members assigned access via Zapier are automatically opted in to marketing and news emails.
Common Use Cases
Here are some popular ways to use Zapier with Uscreen:
Email Marketing: Add new members to Mailchimp, ActiveCampaign, and other email platforms, or trigger personalized email sequences based on member activity
CRM Sync: Update contacts in HubSpot, Salesforce, and other CRMs, and track customer lifetime value
Membership Management: Back up member data to Google Sheets or Excel, or bulk import and assign user access
Community Management: Automatically add new members to Slack, Discord, or Facebook Groups
Content Delivery: Create Buy One Get One Free promotions, or grant access via third-party shop platforms like Shopify and WooCommerce
Payment Processing: Set up custom payment provider integrations with Stripe Checkout
FAQs
Can I segment member accounts I created using Zapier in Uscreen?
Can I segment member accounts I created using Zapier in Uscreen?
Segments in Uscreen are automatically assigned by the system based on a member's subscription activity, and they can't be manually set through Zapier or the admin. However, you can use the User Updated trigger to track changes to a member's segment via the Attributes Segments field.
What happens if my Zap stops working?
What happens if my Zap stops working?
First, check that your Zapier API key is correctly entered under App Connections in Zapier. Also, review any conditions (Filters or Paths) that might be preventing the trigger from firing. Check your Plan tasks to see if your Zapier plan limit has been reached, and review the Zap History for any error messages.
How can I test if my Zapier integration is working?
How can I test if my Zapier integration is working?
When setting up a Zap, Zapier provides a testing feature that will attempt to find existing data in your Uscreen account to verify the connection. The sample payloads shown during setup now match the actual data your Zap will receive in production. If your Zap is active, you can also perform a real action on your store to observe the workflow in action.
My Zap was working before, but is now returning unexpected fields or missing data. What happened?
My Zap was working before, but is now returning unexpected fields or missing data. What happened?
If your Zap was built before April 2026, the example payloads shown during setup may have differed slightly from the actual data Uscreen sends. This has since been corrected, and the setup examples and live payloads now match. We recommend reviewing your field mappings in Zapier to make sure they still align with the current payload structure.
Does Zapier support all Uscreen webhook events?
Does Zapier support all Uscreen webhook events?
Not all webhook events are available as Zapier triggers. Uscreen's direct webhook integration supports additional events beyond what Zapier exposes. If you need an event not available as a Zapier trigger, consider using Webhooks by Zapier with Uscreen's native webhook feature instead.