Scope
This guide covers daily operation for Automation Templates, Nodes & Tools. Availability depends on your tenant package, role and configured providers.
Purpose
Reuse outcome-led workflows and inspect available building blocks.
Adapt nodes, connectors and conditions to the workflow.
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
- State the operating objective and the record, audience, campaign or project in scope.
- Adapt nodes, connectors and conditions to the workflow.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Instantiate tested patterns for recurring operations.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Compare template use, runs, failures and completed outcomes.
Verify the result
Compare template use, runs, failures and completed outcomes. 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
Review permissions and side effects before activation. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.