इस पेज पर
What starts this workflow?
Invoice (filter: failed/overdue).
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 | Tag payment-failed | Add a contact tag | Payment issue |
| 2 | Payment issue | Send an email | Fix in 1 tap |
| 3 | Fix in 1 tap | Send a text message | Wait 2 days |
| 4 | Wait 2 days | Wait before the next step | Still unpaid? |
| 5 | Still unpaid? | Route by a condition | Final reminder |
| 6 | Final reminder | Send a text message | Alert team · payment still failing |
| 7 | Alert team · payment still failing | Notify the team | End of this path |
How the branches work
Still unpaid?
- Still unpaid?.
- 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.
एफ़िलिएट लिंक: आप सब्सक्राइब करें तो हमें कमीशन मिलता है।
