Understanding supported workflow triggers, audience rules, and actions

Last updated: September, 2026

Get the most out of your workflows! This article provides a comprehensive guide to all available audience rules, triggers, actions, and templates. Whether you’re looking to automate routine tasks, streamline community management, or perform bulk actions with ease, this guide will help you understand different options.

Triggers are the starting point of any automation workflow, activating the actions you’ve set up.

Once a workflow is active, it continuously monitors the community for specific activities defined by the trigger. When the specified activity occurs—whether performed by or for a member or non-member—the workflow automatically executes the corresponding actions.

Let’s say you have set the Joined space trigger, which activates whenever a member is added to a space. Once a member joins the space, the workflow will perform actions you’ve set up, like sending a welcome email or adding a tag to the member's profile.

• Non-member support: If the trigger is supported for non-members, it will also activate and perform supported actions for them. The supported triggers include Tag added, Tag removed, Profile field updated, and Form submitted.

• Admin inclusion: Workflows recognize admin activities just like they do for members and moderator roles and activate the trigger. For instance:

  • If the workflow is set with the Published an event trigger, it will also activate when an admin publishes an event and performs actions for them.

  • Similarly, with the Tag added trigger, adding a tag to an admin's profile will automatically execute the associated actions for them.

• Filter conditions: You can use filter conditions for triggers to run the automation workflow only for individuals who meet them.

  • Additionally, for certain triggers such as “Published a post”, you can set up an AI filter to describe your filter criteria in natural language.

  • If an individual does not meet the trigger's filter conditions, the workflow is skipped for them.

📚 To learn more about setting up automation workflows, see our guide here.

Here is a list of available triggers within workflows:

• Joined community: Choose this trigger to perform actions when a member successfully joins the community. 

  • This trigger activates when the member joins the community using any entry point (e.g., invitation links, paywalls, API, etc.) and confirms their profile. 

  • If a member is still in the onboarding journey, this trigger will only occur when they confirm their profile and complete the sign up process.

• Profile field updated: This trigger helps you automate workflow whenever the information in the specific profile field is updated.

  • Setup: In the Inputs section, choose the profile field and audience type. 

  • You can trigger it only when the profile field is updated for members, non-members, or all (including both members and non-members).

• Changed email: Choose this trigger to automate actions when a member’s email address is updated.

• Leveled up: This trigger allows you to automate actions whenever the member reaches a specific gamification level. 

  • Setup: In the Inputs section, choose the level. When a member reaches that level, the trigger will activate and perform an action for the member.

  • If a member receives a large reward that pushes their profile through multiple levels (e.g., from level 3 to level 5), the Leveled up or Leveled down trigger events will occur for each level the member passes through if you have set up workflow for those levels.

• Leveled down: This trigger allows you to automate actions whenever the member’s gamification level decreases. 

  • Setup: In the Inputs section, choose the level. When a member’s level drops to the selected level, the trigger will activate and perform an action for the member.

ℹ️ Note: The Leveled up and Leveled down triggers will only be available if you have enabled the Gamification feature within your community.

• Opened email: Use this trigger to automate actions when a member opens a broadcast or workflow email.

  • Setup: In the Inputs section, select the email type. You can choose from Broadcasts (emails sent through Email Hub) or Workflows (emails sent as a workflow action).

  • Once you choose the email type, you can select the specific email in that category that fires the workflow. Click the Choose Broadcast/Workflow email dropdown and select an email.

• Clicked a link: Use this trigger to automate actions when a member clicks a link within an email.

  • Setup: In the Inputs section, select the email type and email. You can choose from Broadcasts (emails sent through Email Hub) or Workflows (emails sent as a workflow action).

  • Once you’ve selected the email type and email, under Choose link, select a specific link from the email.

  • You can only select one link from the email. To use multiple links, please setup a new workflow.

• RSVP’d to event: Set up this trigger for when a member RSVPs to an event. For paid events, this trigger also occurs after the member successfully purchases a ticket. 

  • Setup: In the Inputs section, choose the entity to define the event, such as all events in the community, space group, space, or a specific event. Then select the input, such as which space or event, for the selected entity.

  • This workflow trigger activates when you RSVP a member to an event or when a member RSVPs to an event on their own. If a member is invited, the trigger activates only after they accept the invite and confirm their RSVP.

• RSVP’d to recurring event: Set up this trigger for when a member RSVPs to a recurring event. For paid events, this trigger also occurs after the member successfully purchases a ticket. 

  • Setup: In the Inputs section, select one of the recurring event series from the list.

  • This workflow trigger activates when you RSVP a member to an event or when a member RSVPs to an event on their own. If a member is invited, the trigger activates only after they accept the invite and confirm their RSVP.

  • This trigger will only activate the first time they RSVP to any event in the recurring series. If they RSVP to one event in the series for the first time and then RSVP to the rest later, the workflow won't trigger for subsequent RSVPs in the same series.

• Event ended for member: Use this trigger to automatically perform actions one hour after an event ends for RSVP'd attendees with a "Going" status. This trigger works for events with any type of location, such as in-person or Circle live events.

  • Setup: In the Inputs section, choose the entity to define the event, such as all events in the community, space group, space, or a specific event. Then choose the input, such as which space or event for the selected entity.

• Event starts in an hour: Use this trigger to automatically perform actions when 1 hour remains until an event starts for RSVP'd attendees with a "Going" status. This trigger works for events with any type of location, such as in-person or Circle live events.

  • Setup: In the Inputs section, choose the entity to define the event, such as all events in the community, space group, space, or a specific event. Then choose the input, such as which space or event for the selected entity.

• Published an event: Use this trigger to automatically perform actions when a member publishes an event.

  • Setup: In the Inputs section, choose the entity, such as all events in the community, space group, or space. Then choose the input, such as which space group or space for the selected entity.

• Attended live event: Use this trigger to automatically perform actions for members who attend a Circle live stream or live room event. This trigger activates once the live event is ended.

  • Setup: In the Inputs section, choose a specific Circle live event.

  • This workflow will trigger regardless of whether the member has RSVP'd, as long as they attended the live stream or live room event.

• Added to access group: Use this trigger to automatically perform actions when a member is added to a specific access group.

  • Setup: In the Inputs section, choose the access group from the list. You can also type the name in the field to quickly search for it and then select the appropriate access group from the list.

  • This trigger activates when a member is added by an admin or through various entry points, such as a paywall or an invitation link.

• Removed from access group: Use this trigger to automatically perform actions when a member is removed from a specific access group.

  • Setup: In the Inputs section, choose the access group from the list. You can also type the name in the field to quickly search for it and then select the appropriate access group from the list.

  • This trigger activates when a member is removed by an admin or by the paywall.

• Joined space: Trigger workflow actions when a member is added to a space, either manually by an admin or moderator or when they join on their own. 

  • Setup: In the Inputs section, choose a specific space from your community.

  • This trigger also activates when a member joins the space via a paywall, an invitation link, or other entry points.

• Removed from space: Activate workflow actions when a member is removed from a space or leaves it on their own.

  • Setup: In the Inputs section, choose a specific space from your community.

• Joined space group: Trigger workflow actions when a member is added to a space group.

  • Setup: In the Inputs section, choose a specific space group from your community.

  • This trigger also activates when a member joins the space group via various entry points, such as a paywall, an invitation link, or other methods.

• Removed from space group: Activate workflow actions when a member is removed from a space group.

  • Setup: In the Inputs section, choose a specific space group from your community.

• Charged for a paywall: Use this trigger to automate actions when a member is successfully charged for a paywall purchase, excluding trials.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger is activated every time a member completes a paywall purchase, whether it's a one-time fee, recurring subscription, or installment pricing.

  • If a member is subscribed to subscription or installment paywalls, it will activate for subsequent payments.

• Subscribed to paywall: Utilize this trigger to automate actions when a member purchases a paywall with a recurring subscription or installment pricing (excluding trials and one-time fee purchases).

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger will only activate once, upon the initial subscription, and will not trigger for subsequent payments.

• Subscription scheduled to cancel: Use this trigger to automate actions when a cancellation for a member’s recurring subscription is initiated and scheduled to cancel at the end of the billing period.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger will fire when the cancellation is initiated.

• Trial scheduled to cancel: Use this trigger to automate actions when a cancellation for a member’s trial subscription is set to cancel at the end of the trial period.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

• Subscription cancelled (previously Unsubscribed from paywall): Use this trigger to automate actions when a member’s paid subscription is cancelled immediately either by you, or the member, or due to a failed payment configuration in Stripe.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger will fire when the subscription is actually cancelled. If a subscription is scheduled to be cancelled at the end of the billing period, a workflow using this trigger will run on the billing period's end date.

  • Deprecated triggers will remain functional for existing workflows but will be hidden for new workflows.

• Subscription resumed: Use this trigger to automate an action when a member resumes a subscription that was scheduled to cancel.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger will not fire if a subscription has already been cancelled.

• Subscription changed: Utilize this trigger to automate actions when a member changes their subscription to a specific paywall.

  • Setup: In the Inputs section, configure the following:

    • Paywall: Select the paywall that triggers the workflow when a member changes their subscription to it.

    • Paywall price (optional): Select the specific pricing option to trigger the workflow only when a member changes their subscription to that price.

      • If you select a paywall price, the trigger fires only when the subscription changes to that specific price. If no price is selected, the trigger fires when the subscription changes to the selected paywall.

• Trial resumed: Use this trigger to automate an action when a member resumes a subscription trial that was scheduled to cancel at the end of the trial period.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

• Installment completed: Use this trigger to automate actions when the final installment payment of a member’s subscription has been made.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

• Trial ended and not converted (previously Ended trial without subscription): Utilize this trigger to automate actions when a member's trial ends without converting to a paid subscription.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • Deprecated triggers will remain functional for existing workflows but will be hidden for new workflows.

• Trial converted: Use this trigger to automate actions when a member’s trial ends and converts to a paid subscription.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

• Trial started (previously Started paywall trial): Use this trigger to automate certain actions when the member subscribes for a paywall trial.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • Deprecated triggers will remain functional for existing workflows but will be hidden for new workflows.

• Coupon used at checkout: Use this trigger to automate actions when a coupon code is applied during checkout by a member or, an admin creating a subscription on behalf of a member.

  • Setup: In the Inputs section, choose the specific paywall or coupon that triggers the workflow. Selecting a paywall as the input will trigger the workflow whenever a coupon is applied to that paywall at checkout.

• Coupon added: Use this trigger to automate what happens when a coupon is added to an existing subscription.

  • Setup: In the Inputs section, choose the specific paywall or coupon that triggers the workflow. Selecting a paywall as the input will trigger the workflow whenever a coupon is added to that paywall's subscription.

• Coupon removed: Use this trigger to automate actions when a coupon is removed from an existing subscription.

  • Setup: In the Inputs section, choose the specific paywall or coupon that triggers the workflow. Selecting a paywall as the input will trigger the workflow when any coupon is removed from the specific paywall subscription.

• Coupon ended: Utilize this trigger to automate actions when a repeating coupon's discount period expires.

  • Setup: In the Inputs section, choose the specific paywall or coupon that triggers the workflow. Selecting a paywall as the input will trigger the workflow when any recurring coupon on that paywall subscription expires.

• Failed recurring payment: Use this trigger to automate actions when a recurring payment fails for a subscription.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

  • This trigger only fires for recurring payments on a subscription, not the initial payment.

• Upsell accepted: Use this trigger to automate actions when a customer purchases an upsell along with a paywall.

  • Setup: In the Inputs section, select the specific paywall (including an upsell) to trigger the workflow.

• Upsell declined: Select this trigger to automate actions when a customer declines an upsell.

  • Setup: In the Inputs section, select the specific paywall (including an upsell) to trigger the workflow.

• Upsell abandoned: Use this trigger to automate an action when an upsell offer is abandoned.

  • Setup: In the Inputs section, select the specific paywall (including an upsell) to trigger the workflow.

• Checkout completed: Use this trigger to automate actions when a member completes the entire checkout flow. This trigger does not require a specific paywall as input.

❗Important: When multiple prices are added within a paywall, the triggers will apply to all prices within that specific paywall.

💡 Tip: To learn more about the paywall-related workflows, see our guide here.

• Tag added: Use this trigger to automate actions for the audience when a tag is assigned to members, non-members, or everyone. 

  • Setup: In the Inputs section, choose the tag and audience type to ensure it applies only to the selected audience type.

• Tag removed: This trigger enables you to automate actions for the audience when a tag is removed from members, non-members, or everyone. 

  • Setup: In the Inputs section, choose which tag and audience type to ensure it occurs only for the selected type of audience. 

• Published a post: This trigger activates when a member publishes a new post. 

  • Setup: In the Inputs section, choose the entity to define the location, such as all new posts published in any post space within the community, a specific space group, or a specific space. Then choose the input for the selected entity.

  • Note that this trigger only activates for post type spaces.

• Posted a comment: Utilize this trigger to automate actions for a member when they comment on a post. 

  • Setup: In the Inputs section, choose the entity to define the location, such as all new comments posted in any post space within the community, a specific space group, a specific space, or a specific post. Then choose the input for the selected entity.

  • Note that this trigger only activates for comments posted within the post type spaces.

• Liked a post: Utilize this trigger to automate actions for a member when they like a post. 

  • Setup: In the Inputs section, choose the entity to define the location, such as all new likes in any post space within the community, a specific space group, a specific space, or a specific post. Then choose the input for the selected entity.

  • Note that this trigger only activates for likes within the post type spaces.

• Post was flagged: Use this trigger to automate actions for a member whose post was flagged by any method, such as a report or a moderation configuration, such as profanity filters.

  • Setup: In the Inputs section, choose the entity to define the eligible posts for this trigger, such as:

    • All posts (in the post type spaces) within the community.

    • All posts (in the post type spaces) in a specific space group.

    • All posts in a specific post space.

    • A specific post.

  • Based on the selected entity, choose the value for the entity.

• Comment was flagged: Trigger actions for a member whose comment was flagged through any method, such as due to a report or moderation configuration, such as profanity filters.

  • Setup: In the Inputs section, choose the entity to define the eligible comments for this trigger, such as:

    • All comments (in the post type spaces) within the community.

    • All comments (in the post type spaces) in a specific space group.

    • All comments in a specific post space.

    • Comments on a specific post.

  • Based on the selected entity, choose the value for the entity.

• Post was approved: Automate actions for the member once an admin or moderator approves their post.

  • Setup: In the Inputs section, choose the entity to define the eligible posts for this trigger, such as:

    • All posts (in the post type spaces) within the community.

    • All posts (in the post type spaces) in a specific space group.

    • All posts in a specific post space.

    • A specific post.

  • Based on the selected entity, choose the value for the entity.

• Comment was approved: Automate actions for the member once an admin or moderator approves their comment.

  • Setup: In the Inputs section, choose the entity to define the eligible comments for this trigger, such as:

    • All comments (in the post type spaces) within the community.

    • All comments (in the post type spaces) in a specific space group.

    • All comments in a specific post space.

    • Comments on a specific post.

  • Based on the selected entity, choose the value for the entity.

• Post was rejected: Use this trigger to automate action for the member when their post fails moderation review. This is great for sending members a DM explaining the reason behind the rejection.

  • Setup: In the Inputs section, choose the entity to define the eligible posts for this trigger, such as:

    • All posts (in the post type spaces) within the community.

    • All posts (in the post type spaces) in a specific space group.

    • All posts in a specific post space.

    • A specific post.

  • Based on the selected entity, choose the value for the entity.

• Comment was rejected: Use this trigger to automate action for the member when their comment fails moderation review. This is great for sending members a DM explaining the reason behind the rejection.

  • Setup: In the Inputs section, choose the entity to define the eligible comments for this trigger, such as:

    • All comments (in the post type spaces) within the community.

    • All comments (in the post type spaces) in a specific space group.

    • All comments in a specific post space.

    • Comments on a specific post.

  • Based on the selected entity, choose the value for the entity.

• Completed course: Use this trigger to automate actions for a member when they complete a course.

  • Setup: In the Inputs section, choose the course space.

  • Please note that:

    • This trigger only activates when a member has completed all the lessons and quizzes part of the course on their own. If an admin removes a lesson or quiz from a course (by deleting it or setting it to draft), and that action marks the course as complete for a member, it will not trigger the workflow.

    • If a member marks any lesson as incomplete after completing the whole course and then completes it again to complete the course, this trigger will activate again. Similarly, if you add a new lesson to the course after the member has already completed it, this workflow trigger will activate again for the member once they complete the lesson and the course again.

• Completed lesson: This trigger activates for a member when they complete a lesson.

  • Setup: In the Inputs section, choose the entity, such as all lessons within the community, all lessons within a space group, all lessons within a specific course space, or a specific lesson. Then choose the input for the selected entity.

  • If a member marks a lesson as incomplete and then completes it again, the trigger will activate again for that member.

• Completed section: Utilize this trigger to automate actions for a member when they complete lessons within a section of a course.

  • Setup: In the Inputs section, choose the entity, such as all course sections within the community, all sections within a space group, all sections within a specific course space, or a specific section. Then choose the input for the selected entity.

  • Please note that:

    • The trigger activates only when a member completes all lessons and quizzes in the section independently. If an admin removes a lesson or quiz (by deleting it or setting it to draft) and that action causes a section to be marked complete for a member, it will not trigger the workflow.

    • If a member marks a lesson as incomplete within a section they already completed and then completes that lesson again, the trigger will activate again for the member.

• Passed quiz: This trigger activates for a member when they pass a quiz within a course.

  • Setup: In the Inputs section, choose the entity, such as all quizzes within the community, all quizzes within a space group, all quizzes within a specific course space, or a specific quiz. Then choose the input for the selected entity.

  • This trigger only automatically activates if you have set a passing grade for the quiz. If you haven't set a passing grade, this trigger will only activate after you manually grade the quiz and indicate that the member passed.

• Failed quiz: Utilize this trigger to automate actions for a member when they fail a quiz within a course.

  • Setup: In the Inputs section, choose the entity, such as all quizzes within the community, all quizzes within a space group, all quizzes within a specific course space, or a specific quiz. Then choose the input for the selected entity.

  • This trigger only automatically activates if you have set a passing grade for the quiz. If you haven't set a passing grade, this trigger will only activate after you manually grade the quiz and indicate that the member failed.

• Submits quiz: This trigger activates when a member submits a quiz within a course, regardless of whether they passed or failed. 

  • Setup: In the Inputs section, choose the entity, such as all quizzes within the community, all quizzes within a space group, all quizzes within a specific course space, or a specific quiz. Then choose the input for the entity.

• Form submitted: This trigger activates when a member or non-member submits the published form.

  • Setup: In the Inputs section, choose the form from the list.

  • This trigger is only available with Email Hub. If you have canceled the Email Hub subscription, the workflow containing this trigger will also be disabled.

• Admin received a direct message: This trigger activates when a member sends a direct message to a particular admin. It’s useful for setting up automated actions, like sending an automated response using the Send a Direct Message action.

  • Setup: In the Inputs section, choose the name of the admin from the list.

  • This trigger activates once per member within a 1-hour window. After triggering, additional messages from the same member won’t reactivate it for one hour.

Available in the Entry rule step, audience rules are essential for targeting specific groups of people in bulk actions and scheduled workflows. They allow you to define a customized audience of members or non-members (when supported by audience rules), ensuring that your workflows deliver the right actions to the right individuals.

For example, you might create an audience based on a combination of a specific tag and a gamification level rule. Once defined, these audience rules ensure your workflow actions, such as adding them to a space or sending an email, are applied only to the selected group. When the workflow runs, it executes these actions for everyone who matches the criteria defined in your audience rules.

• Admin and moderator inclusion: Admin and moderator accounts are included in the workflow audience if they meet the audience rule's criteria. To exclude admins or moderators, use the Role audience rule and select Members to target only member roles.

• Non-member support: If the audience rule applies to non-members and they meet the specified criteria, they will also be included in the workflow audience. For example, you can make use of rules such as profile field, segment, or tag to target non-members as well.

• Audience rules use “And” conditions: Rules are applied with the “And” condition, meaning criteria from all applied rules must be met for an individual to be included in the workflow audience.

  • You can further refine your audience by applying the same filter multiple times, creating a combination that narrows down results to a granular level. For instance, apply the tag rule twice with two different tags to only include individuals who have been assigned with both tags.

  • Advanced conditions for rules: These conditions are available to text-type and list-type audience rules, such as name, headline, and location (including checkbox and dropdown-type profile fields). Depending on the type of field you are using as an audience rule, you can use one of the following conditions:

    • Contains (available only to text, link, and number type fields)

    • Does not contain (available only to text, link, and number type fields)

    • Is

    • Is not

    • Is empty

    • Is not empty

📚 For more information about setting up bulk action workflows, see our guide here. For scheduled workflows, check out Schedule a bulk action workflow.

Here is a list of available audience rules within workflows:

• Segment: Use pre-saved audience segments as criteria to quickly define your audience. This rule allows you to apply previously configured segments to target specific groups effortlessly.

  • Setup: Choose from one of the existing segments. Alternatively, use the search bar above the list to find a specific tag and then select it from the list.

• Tag: Identify individuals by the tags assigned to them. This rule includes both members and non-members.

  • Setup: Choose from one of the existing tags. You can also use the search bar above the list to find a specific tag and then select it from the list.

  • If you want to target individuals assigned multiple tags, apply the tag rule to each tag.

• Name: Target specific individuals by their name, whether they are members or non-members.

  • Setup: Select one of the advanced conditions, such as is or is not, and enter the value.

• Email marketing: Define your audience based on their email marketing subscription status. This will let you filter the audience based on whether they are contact or not.

• Email: Locate members or non-members using their email address to refine your audience selection.

  • Setup: Select one of the conditions, such as is or is not, and enter the value.

• Member: Target individuals based on their membership status. This allows you to choose whether your audience consists of community members or non-members. 

  • Setup: Choose the yes or no option.

  • When you select the rule value "Yes," the audience will include only members who have completed the sign up process by confirming their profiles. If you choose the rule value "No," the audience will include non-members as well as members who have not yet confirmed their profiles.

• Invitation status: Refine your audience by the current stage of their onboarding journey, such as whether they’ve been invited or have created an account. This rule only applies to community members who are assigned a specific status in their invitation journey.

  • Setup: Select one of the invitation statuses to filter the audience by members who are currently assigned to that status.

• Headline: Narrow your audience using the headline text displayed on members’ profiles. 

  • Setup: Select one of the conditions, such as contains, and enter the value to target members with a headline containing that value.

• Role: Refine your audience based on assigned roles such as admin, moderator, or member. 

  • Setup: Select the desired role from the list.

  • This rule allows you to target community members with specific roles and includes individuals with assigned roles who have not yet confirmed their profiles.

• Space: Define your audience by whether they are members of a specific space. 

  • Setup: Select the appropriate space from the list. You can also use the search bar above the list to find a space and then select it from the list.

  • If you want to target members who belong to multiple spaces, apply the space rule for each space.

• Space group: Define your audience by whether they are members of a specific space group. 

  • Setup: Select the appropriate space group from the list. You can also use the search bar above the list to find a specific group and then select it from the list.

  • If you want to target members who belong to multiple space groups, apply the space-group rule to each group.

• Invitation link: Use this rule to only include members who joined the community through a specific invitation link in the audience.

  • Setup: Select the invitation link from the list. Alternatively, use the search bar above the list to find a specific link and then select it from the list.

  • You can choose the link that is currently disabled to filter members who may have joined the community in the past when the link was active. 

• Status: Filter the audience by community members who are either currently online or offline in your community.

• Subscribed to paywall(s): Target individuals who are subscribed to a specific paywall. 

  • Setup: Select one of the paywalls from the list. The list includes both active and archived paywalls.

  • This rule includes members who have purchased a recurring subscription, installments, or one-time fee paywalls (excluding members who are refunded with a full one-time fee amount).

  • When you select a paywall, all of its prices will be considered when defining the audience.

• Event: Find members who confirmed their RSVP to a specific event, whether upcoming or past. 

  • Setup: Select the event from the list. Alternatively, use the search bar above the list to find a specific event and then select it from the list.

  • Each event will appear with a time stamp and will be categorized in the upcoming and past sections to help you easily identify it.

  • Any member in “Invited” status or who has set their RSVP status to “Not going” will be excluded from the audience.

• Past due subscription: Identify members whose subscriptions are currently in a past due status. This status indicates that Stripe attempted to charge them for their ongoing paywall subscription or installment but for some reason, it failed, which moved their status to past due.

  • Setup: Choose the yes or no option.

• Join date: Refine your audience by selecting community members based on their join date.

  • Setup: Utilize the less than, equals to, or greater than condition and enter the value to define the rule. 

  • This join date indicates the date when members confirmed their profile and completed the sign up process.

• Last logged in: Target members based on when they most recently logged in to the community. 

  • Setup: Utilize the less than, equals to, or greater than condition and enter the value to define the rule. 

• Has profile photo: Target community members who have uploaded a profile photo.

  • Setup: Choose the yes or no option.

• Activity score: Target community members using their engagement level as measured by activity scores. 

  • Setup: Use the slider to select a specific score range with min and max values.

• Level: Refine your audience by a specific gamification level that members are currently at within the community. 

  • Setup: Choose one gamification level from the list.

  • The Level rule will only be available if you have enabled the Gamification feature within your community.

• Access group: Define your audience based on whether they are members of a specific access group. 

  • Setup: Select the appropriate access group from the list. You can also use the search bar above the list to find an access group and then select it from the list.

  • If you want to target members who belong to multiple access groups, apply the access group rule for each access group.

You can define your audience using both default and custom profile fields. This is a great way to refine your audience by profile field values.

When you utilize profile fields as audience rules, you can target both members and non-members, provided that their profile field information matches the audience rule conditions. 

When setting up a profile field audience rule, choose the advanced conditions appropriate to the rule's nature and enter your desired value.

Actions are the tasks a workflow performs based on the triggers or entry rules you’ve set.

• Automation workflows: Actions in automation workflows are triggered by specific activities performed by or for members or non-members (if the trigger supports non-members). Once the trigger conditions are met, the workflow automatically executes the defined actions.

• Bulk actions workflows: In bulk or scheduled workflows, actions are applied to an audience defined by the Entry rule step. Depending on the entry rule setup, this audience can include both members and non-members.

• Non-members in workflow: Non-members are included in workflow actions only if those actions are supported for them. Examples include sending marketing emails, adding or removing tags, or unsubscribing non-members from marketing emails.

• Multiple actions: Workflows support multiple actions, allowing you to configure several tasks within a single workflow. These tasks are executed sequentially in the same order in which they are configured within a workflow.

• Task executions: Actions performed by workflows can result in varying outcomes depending on the scenario, including partial success, being skipped, or failure. Failures can occur due to errors during execution, the action not being supported for certain individuals (e.g., non-members), or the individual being ineligible. You can learn more about task history here.

• Filter conditions: Set filter conditions for actions to only let the workflow perform actions for individuals who meet the specified conditions. If your workflow has multiple actions, you can set filter conditions for each one.

  • ℹ️ Note: You can utilize filter conditions for any action except Time delay and ones that are part of the AI actions.

Here is a list of available actions within workflows:

• Agent comments on post: Choose this action to allow your AI agent to automatically comment on a member’s post when the workflow is triggered.

  • Setup: In the Inputs section, select the agent and response rate, provide instructions (up to 1500 characters) in the AI prompt, and choose where to skip the agent’s response if another member has already answered.

• AI reports post: This action automatically reports a post that triggers the workflow. This action is really useful to implement AI moderation.

  • Setup: In the Inputs section, you can flag the post for review and hide it until approved. You can also add a reason for the report by entering a manual explanation (up to 500 characters) or letting AI generate a context-specific reason. This reason appears in the report when an admin or moderator reviews the flagged post.

• AI reports comment: This action automatically reports a comment that triggers the workflow. This action is really useful to implement AI moderation similar to posts.

  • Setup: In the Inputs section, you can flag the comment for review and hide it until approved. You can also add a reason for the report by entering a manual explanation (up to 500 characters) or letting AI generate a context-specific reason. This reason appears in the report when an admin or moderator reviews the flagged comment.

• AI renames post title: This action uses AI to rename the title of the post that triggers the workflow.

  • Setup: In the Inputs section, provide instructions (up to 500 characters) within the AI prompt field on how the title should be updated.

• Agent sends direct message: Use this action to have your AI agent send a direct message to a member.

  • Setup: In the Inputs section, select the agent and add your instructions (up to 500 characters) in the AI prompt field.

• AI edits topics: This action uses AI to analyze the content of a published post and automatically assign the most relevant topics.

  • Setup: In the Inputs section, configure the following:

    • Exclude these topics (optional): Enter any topics you want AI to exclude.

    • Behavior: Choose how AI assigns topics:

      • Assign at least one topic: AI assigns the most relevant topic to the post.

      • Don’t assign any topics when there are no clear matches: AI skips topic assignment if it can’t confidently match one.

📚 To learn more about AI actions, see Setting up AI filters and actions.

• Send an email: Choose this action to send a marketing email to members and non-members. This action is only performed for contacts who are subscribed to email marketing.

  • Setup: In the Inputs section, add the subject line, preview text, and write email content using the text or visual builder. For more information, see Set up email workflows.

  • Once you activate the automation workflow or run the bulk action workflow, you can also view its performance from the workflow overview page.

  • This action is only available with Email Hub. If you have canceled your Email Hub subscription, any workflow containing this action will also be disabled.

• Send a direct message: This action lets you send messages directly to your community members.

  • Setup: In the Inputs section, set the sender and add your message.

    • From: You can assign yourself, one of the admins, or moderators as a sender. By default, you will be assigned as a sender. To assign someone else, click the From field, start typing their name, and select from the list. 

      • If the selected admin is removed or loses admin privileges, the workflow will automatically reassign another admin as the sender. When this happens, all community admins will receive an email notification informing them of this change so you can review and update the workflow if needed.

    • Message body: Enter your message in the text field.

      • You can use dynamic variables to personalize the message by automatically inserting relevant information. These variables can pull information from the member, your community, and posts or comments (when a post- or comment-related trigger is chosen), as well as the rejection note for post- or comment-moderation triggers.

      • To add a line break in the message body, use the Shift + Enter shortcut key.

      • You can apply styles like bold, italic, strikethrough, underline, or add hyperlinks to text. To access the formatting toolbar, select the text. You can also use keyboard shortcuts like Cmd/Ctrl + B for bold and similar commands for other styles.

      • To include emojis, type a colon (:) followed by the emoji's name to search and select it from the list.

    • Preview direct message: Click Preview message under the message body to see how it will appear to recipients.

• Send mobile push notification: Use this action to send a custom mobile push notification to your members. 

  • Setup: In the Inputs section, set up the following:

    • Circle URL: Enter the URL of any specific area within your community, such as a space, lesson, post, or event. For instance, if you want the push notification to link to an event, use the event’s URL. For the URL “https://mycommunity.circle.so/c/events/meetups”, simply enter “c/events/meetups” in the field.

    • Message body: Write a concise notification message of up to 150 characters. To include emojis, type a colon (:) followed by the emoji's name to search and select it from the list.

  • This action only works for members who have completed the sign-up process by confirming their profile and are logged in to the community's Android or iOS mobile app.

• Unsubscribe from email marketing: Utilize this action to unsubscribe members and non-members from email marketing.

  • After unsubscribing, members or non-members must manually resubscribe to marketing emails. They can also submit a form to resubscribe. If you re-import contacts who are already unsubscribed, it won’t resubscribe them.

• Add tag: Assign a specific tag to individuals, including members or non-members.

  • Setup: In the Inputs section, select a tag that you would like to assign. You can also type the name in the field to quickly search it and then select the appropriate tag from the list.

• Remove tag: Remove a specific tag from individuals, including members or non-members.

  • Setup: In the Inputs section, select a tag you want to remove. You can also type the name in the field to quickly search it and then select the appropriate tag from the list.

• Remove member(s) from community: This action deactivates the member’s community account.

  • ❗ Important: Deactivating a member's account will remove their access to the community. All their profile data is permanently deleted, and any active paywall subscription or installments are canceled. However, their posts, comments, and messages in chat spaces and group DMs will remain visible in the community.

    • For more details on what happens when a member’s account is deactivated and what data is removed, see our guide here.

• Enable direct messaging: Enable members’ ability to send and receive DMs from other community members.

• Disable direct messaging: This action restricts a member’s ability to send and receive direct messages (DMs) with other community members.

  • Even if a member's DM capabilities are disabled, admins can still send them messages, and members can respond to admin-initiated DMs. However, members cannot:

    • Start new DMs.

    • Send DMs to other members.

    • Receive DMs from other members.

  • For more information, see our guide here.

• Add member to space: Provide your member with access to a specific space.

  • Setup: In the Inputs section, select a space to which you would like to add members. You can also type the name in the field to quickly search for it and then select the appropriate space from the list.

• Remove member from space: Use this action to revoke members’ access from a specific space.

  • Setup: In the Inputs section, select a space from which you would like to remove members. You can also type the name in the field to quickly search for it and then select the appropriate space from the list.

• Add member to space group: Use this action to give your members access to a specific space group.

  • Setup: In the Inputs section, select a space group to add members to. You can also type the name in the field to quickly search it and then select the appropriate space group from the list.

• Remove member from space group: Use this action to revoke members’ access from a specific space group.

  • Setup: In the Inputs section, select a space group you would like to remove members from. You can also type the name in the field to quickly search it and then select the appropriate space group from the list.

ℹ️ Note: When you add or remove members from spaces or space groups using workflow actions, members won’t get notified.

• Add member(s) to access group: Use this action to automatically add your members to a specific access group, granting them access to all spaces included in the group.

  • Setup: In the Inputs section, select the access group to which you would like to add members. You can also type the name in the field to quickly search for it and then select the appropriate access group from the list.

• Remove member(s) from access group: Use this action to automatically remove your members from a specific access group, revoking their access from spaces included in the group.

  • Setup: In the Inputs section, select the access group from which you would like to remove members. You can also type the name in the field to quickly search for it and then select the appropriate access group from the list.

ℹ️ Note: When you add or remove members from access groups using workflow actions, members won’t get notified.

• Send to webhook: Use this action to automatically send data from the triggered event within your community to a custom endpoint URL within your application.

  • Setup: In the Inputs section, enter your endpoint URL and a description of the purpose of this webhook endpoint.

  • This action is only available in automation workflows.

• Cancel paywall subscription: Use this action to cancel a member's recurring paywall subscription at the end of their current billing cycle.

  • Setup: In the Inputs section, choose the paywall from which you would like to cancel a member’s subscription.

• Cancel subscription immediately: Use this action to cancel a member's recurring paywall subscription immediately.

  • Setup: In the Inputs section, choose one of the active paywalls from the list.

• Subscribe to paywall trial: Use this action to enroll members in a paywall trial.

  • Setup: In the Inputs section, configure the following:

    • Paywall and price: Select the desired paywall and a supported pricing option. You can select a recurring subscription or installment pricing without upfront payments. This will be the price that members will pay if they decide to continue with a paid subscription or an installment plan.

    • Trial days: Enter the custom trial duration dedicated to this action, up to a maximum of 730 days.

    • Notification: Choose whether to send members an email notification about trial initiation by toggling the Send member(s) a trial started email confirmation option.

  • Adding custom trial days for this action will not override or depend on your paywall’s trial settings or credit card requirements. Meaning, that members will receive the trial duration specified here without needing to provide credit card information upfront. If payment details are not provided before the trial ends, their membership will be canceled according to the configured retry schedule.

• Add coupon to subscription: Use this action to add a coupon to a member’s subscription.

  • Setup: In the Inputs section, configure the following:

    • Coupon: Select a coupon to add to a member’s subscription.

    • Paywall (optional): For more control, you can also select a paywall to choose exactly which subscription the coupon applies to.

    • If a coupon is already applied to the subscription, this action replaces the existing coupon.

• Remove coupon from subscription: Use this action to remove a coupon from a member’s subscription.

  • Setup: In the Inputs section, configure the following:

    • Paywall: Select a specific paywall to remove a coupon from.

    • Coupon (optional): For further control, you can also select a specific coupon to remove from a member’s subscription.

    • If no coupon is selected, any applied coupon is removed.

• Change subscription: Use this action to change a member’s subscription to another paywall or pricing option within the same subscription group.

  • Setup: In the Inputs section, select the Paywall and Paywall price to update the member’s subscription to.

• Edit post settings: This action lets you modify specific settings for a post that triggers the workflow.

  • Setup: In the Inputs section, enable or disable the toggle for settings such as: Hide meta info, Close comments, Disable truncation, Change space and Change post author.

  • ❗ Important: Please note that this workflow action only turns toggles on. It does not switch them off. For example, if a post already has “Close comments” turned on, and the workflow action has it off, the workflow won’t undo the existing setting.

• RSVP or invite member(s) to event: Use this action to add members to a specific event. This is a great way to drive engagement and ensure participation in your community’s events.

  • Setup: In the Inputs section, choose the event. You can also type the name in the field to quickly search for it and then select the appropriate event from the list.

    • Each event will include basic information to help you easily identify it, such as the event space, date, and price (for paid events).

  • ❗Important: How this action works depends on your event settings.

    • If the event’s People tab has the Automatically RSVP invited attendees toggle turned on, this action will RSVP the member. In this case, make sure you’ve enabled the confirmation email notification in your event setup so they receive it.

    • If that toggle is off, the member will receive an invite instead. The email includes a link to view the event details, where they can accept to confirm RSVP or decline the invite directly.

• Time delay: Time delay allows you to introduce a specific pause before the workflow proceeds to the next action in the sequence. This can help space out actions for better timing and member experience. 

  • Setup: In the Inputs section, choose the type of duration and the amount of time. 

  • For instance, if you want to add one day of delay before the workflow sends a DM to a member, add the Time delay action right before the Send a direct message action. For more information on time delays, see our guide here.

• Reward points: This action lets you award custom gamification points to members, encouraging engagement and participation.

  • Setup: In the Inputs section, enter the number of points (you can add up to 500 points) and a reason for rewarding points.

  • Once this action is performed, members will receive an in-app notification about the reward. 

  • The rewarded points will also be visible in the member’s profile under the Rewards tab. To learn more, see our guide here.