इस पेज पर
What starts this workflow?
Contact Updated Trigger, Contact Created Trigger.
The workflow, step by step
The table shows the saved connections. Branches are alternative paths, not a single sequence that every contact follows.
| Step | Action | What it does | Next step |
|---|---|---|---|
| 1 | Website Field Present? | Route by a condition | Website Exists |
| 2 | Website Exists | Route by a condition | Website Not Present |
| 3 | Website Not Present | Route by a condition | Assign 'audit-website' Tag |
| 4 | Assign 'audit-website' Tag | Add a contact tag | Assign 'no-website' Tag |
| 5 | Assign 'no-website' Tag | Add a contact tag | End of this path |
How the branches work
Website Field Present?
- Check if Contact Website Field is Present and Not Empty.
- Otherwise: None.
The labels above come from the saved builder. Review the actual condition values in your own account before activation.
Connect it to your business
- Import into a test sub-account and keep the workflow unpublished.
- Connect the trigger to your actual form, calendar, pipeline or contact tag.
- Review the messages and replace all business, booking and review placeholders.
- Connect any sender, phone number, team member or external integration used by the steps.
- Test each branch, replies, contact restrictions and repeat enrollment with contacts you control.
Get the library
Start GoHighLevel through the RocketLauncher partner link and join the community for snapshot access and setup help. This draft must pass its setup and execution checks before activation.
एफ़िलिएट लिंक: आप सब्सक्राइब करें तो हमें कमीशन मिलता है।
