Communities

Automate Community group join requests

Automate how your organization handles requests to join a Community group by starting a workflow when a member submits a join request, then using the answers to their membership questions to approve, reject, or route the request.

Before you start

The Requested to Join Group trigger starts only for join requests, so the group must use request-based access. Private groups require review of every join request, while public groups let people join immediately. For the difference, see Make groups private in Communities.

Create a join-request workflow

Start in the Workflow Builder and add the Requested to Join Group trigger from the Communities category.

  1. Open the Workflow Builder.

  2. Add a new trigger and open the Communities category.

  3. Select Requested to Join Group.

  4. Set the required Group filter.

  5. Add Membership Question Responses filters to match the answers you want to act on.

  6. Add the workflow actions and select Save Trigger.

Filter by membership question responses

Use the membership-question filters to act only on requests whose answers meet your criteria. The filters appear after you select a group and reflect the membership questions configured for that group; if the group has no membership questions, the filter does not appear. Responses are available throughout the workflow, not only in the trigger, so you can use them in later steps.

Approve, reject, or route requests

Add logic and actions after the trigger to decide what happens to each request.

  • If/Else branches let you apply different outcomes to different answers.

  • A GPT action can evaluate answers for spam, gibberish, or low quality. GPT actions incur additional charges per execution.

  • Grant Group Access approves a qualifying request by granting the member access to the group.

  • Send a welcome message, apply a tag, or notify an admin to handle requests that need attention.

How the member experiences a join request

The member-facing join-request experience is unchanged; automation happens behind the scenes.

  1. A member opens the private group and selects Request to join.

  2. The button changes to Membership Pending while the request awaits review.

  3. If the group has membership questions, the member answers them as part of the request.

  4. The workflow receives the request and its responses and processes it according to your logic.

Admins can still review requests manually through Members > Requested. For the manual approval flow, see Manage community group members.

Was this helpful?
Was this helpful?