このページの内容
What starts this workflow?
Trigger needs configuration.
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 | Create Opportunity · 01 New Lead | Internal create opportunity | Add Tag "frontdoor_ai" |
| 2 | Add Tag "frontdoor_ai" | Add a contact tag | yes |
| 3 | Call Outcome | Route by a condition | BOOKED / TRANSFERRED / HOT / URGENT / CALLBACK / ABANDONED / NURTURE / None |
| 4 | BOOKED | Route by a condition | Update opportunity · 03 Booked |
| 5 | Update opportunity · 03 Booked | Update a pipeline opportunity | Internal Notification · email |
| 6 | Internal Notification · email | Notify the team | End of this path |
| 7 | TRANSFERRED | Route by a condition | Update opportunity · 04 Transferred |
| 8 | Update opportunity · 04 Transferred | Update a pipeline opportunity | Internal Notification · email |
| 9 | Internal Notification · email | Notify the team | End of this path |
| 10 | HOT / URGENT | Route by a condition | Update opportunity · 02 Qualified (Hot) |
| 11 | Update opportunity · 02 Qualified (Hot) | Update a pipeline opportunity | Internal Notification · email |
| 12 | Internal Notification · email | Notify the team | Task · Call within 15 minutes |
| 13 | Task · Call within 15 minutes | Task-notification | End of this path |
| 14 | CALLBACK | Route by a condition | Update opportunity · 05 Callback Scheduled |
| 15 | Update opportunity · 05 Callback Scheduled | Update a pipeline opportunity | Internal Notification · email |
| 16 | Internal Notification · email | Notify the team | Task · Callback within 24h |
| 17 | Task · Callback within 24h | Task-notification | yes |
| 18 | Call Outcome | Route by a condition | Yes / No |
| 19 | Yes | Route by a condition | SMS |
| 20 | SMS | Send a text message | End of this path |
| 21 | No | Route by a condition | End of this path |
| 22 | ABANDONED / NURTURE | Route by a condition | Update opportunity · 06 Nurture |
| 23 | Update opportunity · 06 Nurture | Update a pipeline opportunity | Task · Missed call · try once |
| 24 | Task · Missed call · try once | Task-notification | yes |
| 25 | Call Outcome | Route by a condition | Yes / No |
| 26 | Yes | Route by a condition | SMS |
| 27 | SMS | Send a text message | End of this path |
| 28 | No | Route by a condition | End of this path |
| 29 | None | Route by a condition | Internal Notification · email |
| 30 | Internal Notification · email | Notify the team | End of this path |
How the branches work
Call Outcome
- BOOKED.
- TRANSFERRED.
- HOT / URGENT.
- CALLBACK.
- ABANDONED / NURTURE.
- Otherwise: None.
SMS consent
- Yes.
- Otherwise: No.
SMS consent
- Yes.
- Otherwise: No.
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.
アフィリエイトリンク：ご契約いただくと、私たちに報酬が入ります。
