Group Access Revoked Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Group Access Revoked trigger fires whenever a contact loses access to a community group. Use it to send notifications, update CRM tags, and run offboarding sequences without manual cleanup.

The Group Access Revoked trigger fires when a contact's access to a community group is removed. Use it to notify the contact, run offboarding sequences, and update internal records so reporting and access stay clean.

What the trigger does

It activates a workflow when a Sparkforge community revokes a contact's access to a group — whether that revocation is manual, payment-driven (canceled subscription), or run by another workflow.

Configure the trigger

  1. Open the Workflow Builder.
  2. Click Create a Workflow.
  3. Add the Group Access Revoked trigger.
  4. Pick the specific group whose revocation should fire the workflow.
  5. Add downstream actions — notifications, tag removals, internal alerts.
  6. Test, save, and activate.

Example: networking group offboarding

A user violates community guidelines in a professional networking group, so an admin revokes their access to the Job Postings group. The workflow sends them a clear notification, removes their Job Postings Member tag, and assigns a task to the community manager to follow up if needed.

Frequently Asked Questions

What kinds of revocations does the trigger catch?
Manual admin revocations, automated revocations from other workflows, and revocations driven by payment events like a canceled subscription.
Can I send a customized message based on the reason for revocation?
Yes. Use If/Else branches keyed on tags, custom fields, or the contact's payment status to send different messages by reason.
How do I clean up CRM tags during offboarding?
Add a Remove Tag action and an Update Custom Field action so reporting and segmentation reflect the lost access immediately.
Does this trigger work alongside Group Access Granted?
Yes. They are independent triggers, so you can run granted/revoked workflows in parallel without conflict.

Was this article helpful?