Nesta página
What starts this workflow?
Daily digest schedule (recurring).
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 | Pull daily metrics from ops endpoint | Send data to a connected service | AI write the owner digest |
| 2 | AI write the owner digest | Generate an AI response | Send digest to owner |
| 3 | Send digest to owner | Notify the team | Post digest to Slack ops channel |
| 4 | Post digest to Slack ops channel | Notify the connected Slack channel | Archive digest to ops log |
| 5 | Archive digest to ops log | Send data to a connected service | End of this path |
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.
