Scope
This guide covers automation for Growth Hub. Availability depends on your tenant package, role and configured providers.
Purpose
A portfolio view of active marketing work, risks and next actions.
Surface scheduled and event-driven work in one queue.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Complete the manual workflow successfully before enabling repeat execution.
- Surface scheduled and event-driven work in one queue.
- Define the trigger, eligibility conditions, action and intended output.
- Add a failure path, owner, retry rule and stop condition.
- Run a controlled test and inspect every generated record or delivery event.
- Keep the automation bounded: Respect project access, ownership and approval boundaries.
Verify the result
Read campaign, lead, channel and task movement together. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Respect project access, ownership and approval boundaries. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.