> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/membership-triggers-overview-for-the-workflow-builder.md).

# Membership Triggers Overview for the Workflow Builder

The membership triggers within Workflows allow you to automate features using “if, then” scenarios so that “if” something occurs, “then” one or more action is triggered to occur. We have several tutorials that provide great overviews on the concept of triggers, as well as Workflows, so check them out to learn more if you need an overview of each!

In this article specifically, we will focus on the membership triggers within the Workflow builder.

**Step 1: What are the Membership Trigger Options?**

* **Category Completed:** runs when a category of specified product gets completed
* **Membership New Signup:** a customer/lead subscribed for a membership
  * This will provide both email AND password, only on the initial sign-up.
* **Offer Access Granted:** runs when access to offer is granted
* \*\*Offer Access Removed:\*\*runs when access to offer is removed
* **Product Access Granted:** runs when access to product is granted
* **Product Access Removed:** runs when access to product is removed
* **Product Completed:** runs when product is completed
* **User Login:** runs when user logs in to membership

**Step 2: How To Use the Membership Triggers**

* Navigate into a Workflow.
* Click “Add New Workflow Trigger” at the top.
* In the popup on the right, name your Workflow Trigger (optional).
* Choose a Workflow Trigger from the dropdown (scroll towards the bottom of the list for Membership Triggers).
* Click “Save Trigger” to add the trigger to your Workflow.

{% embed url="<https://lh4.googleusercontent.com/6inUtvR1c3sxcme6BFPUfRYfUz-t0NB3iE8oQ7V1IoSTrOM59a0zloIrrhY4xkGcxQEkDwqa4INkYKO32PhWaB3reFb8fM005NtvAysEScZ-FwHaANnA18ydrqydhffdT7ypchA>" %}

**Pro Tips:**

* In Workflows, you can have several triggering events set to fire off the same series of actions. Perhaps you want one Workflow to run when an **Offer Access** is **granted** or a **Product** **Access** is **granted**. Both triggers can be used in the same workflow.

{% embed url="<https://lh5.googleusercontent.com/eTGjihsaGgRxPyxVi4DxwknurLvIQHpTnmif62ihj6dRY9bGDvoMfu3AGxAwvdAJqZKYjXX-bJgpOfGXG84LJoF7KdGd-wgO9kmHnTdqniDKArzfHnsLBKOEJHON84r-Ki-Y2uc>" %}

* You can add filters to the Workflow triggers to add further specification for how they operate. When adding a Workflow Trigger, click “Add filters” and choose one or more. (In the example below, we filtered out a specific product so the Workflow would run when a specific product access is granted. Without this specification of a particular product, the trigger would run for any product access granted.)

{% embed url="<https://lh3.googleusercontent.com/-dVUWimwd6rmRiKxlgLk5ss_pEu2C8s2aoioQSUV6kdtNlt1Rapb8IoJDzGHN6merurpWOsIFcGR7D4LFD4xHUg3wf5I3SfeUOAT5mlaJsU-40nHvnlfl2BA4xUJj0XcDAHsp5I>" %}

{% embed url="<https://lh5.googleusercontent.com/Leo_o46oCMXkCY8xaftMkvM3qUsqJGb124tM5qxIcEnD-IMJUd28YxTp__Vitlai3dL3jDzDeoBaG4t2vZIVxCklem7ltXxH0TEw-322aAAi1c2ATkewNn4nOg78xb3jTzlrk9k>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/membership-triggers-overview-for-the-workflow-builder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
