Scope
This guide covers daily operation for Connectors, APIs & Webhooks. Availability depends on your tenant package, role and configured providers.
Purpose
Connect CRM, commerce, analytics, messaging and developer systems.
Map resources, monitor sync and handle integration errors.
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.
- Map resources, monitor sync and handle integration errors.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Move eligible events and records through scheduled or event flows.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review sync health, latency, failures and downstream use.
Verify the result
Review sync health, latency, failures and downstream use. 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
Use least privilege, signature checks and credential rotation. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.