For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to Set Up a Workflow in GHL

Let's look at a few examples of how to set up a workflow.

Use only this trigger: Contact changed — triggered by any change in the customer card (custom fields).

Option 1: Card Issue

If the card has just been issued (generated):

  • Select a custom field as a condition Install Link.

  • Condition: Install Link → has changed (changed).

  • This means that the installation link has appeared → the card has been issued.

For example,

Option 2: Installing the card

If the card was installed by the user:

  • Use a custom field Card Status.

  • Condition: Card Status → has changed to Installed.

  • This confirms the fact that the card has been installed.

✅ If the field value was previously empty and became non-empty, this can also be used as an indication of installation.

For example,

Option 3: Tracking balance and stamps

Balance (e.g. cashback or bonuses):

  • Find the Reward or Bonus Balance field (the name depends on the card type).

  • Condition: Reward → has changed.

Stamps:

  • Use the field Number of Stamps or Total Stamps.

  • Condition: Number of Stamps → has changed.

The names of the fields may differ depending on the card template (stamped, bonus, etc.).

An example where the total number of customer stamps changes.

❗️Important: Pay attention to the card identifier. Each card has its own identifier.

This is a standard workflow setup process. Follow the instructions in GHL for further details.

Next you can add the actions that GHL suggests.

In addition, you can use our actions

Last updated