Nesta página
What starts this workflow?
Contact created / updated.
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 | Missing contact info | Route by a condition | Missing email · flag |
| 2 | Missing email · flag | Add a contact tag | Request email via SMS (if phone exists) |
| 3 | Request email via SMS (if phone exists) | Manual-sms | Missing phone · flag |
| 4 | Missing phone · flag | Add a contact tag | Request phone via email (if email exists) |
| 5 | Request phone via email (if email exists) | Send an email | Flag incomplete record to ops |
| 6 | Flag incomplete record to ops | Notify the team | Send to ops for dedup / enrichment |
| 7 | Send to ops for dedup / enrichment | Send data to a connected service | End of this path |
How the branches work
Missing contact info
- Missing email.
- Missing phone.
- Otherwise: Clean · pass.
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.
Link de afiliado: ganhamos uma comissão se você assinar.
