Guide a new client through data integration
Run a maintained onboarding procedure that combines client questions, data validation, configuration, and human approval.
How this works
Run a maintained onboarding procedure that combines client questions, data validation, configuration, and human approval.
Treat onboarding as a series of verified data contracts rather than a checklist of connected accounts. Choose the project-specific path, establish field meaning and confirm an actual refresh reaches the intended output before calling the integration ready.
Before you start
Defined operating scope
Client delivery depends on agreeing data definitions and validating integrations during setup.
Required source material
Obtain Sales handover; Project type and source systems; Maintained integration procedures. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The handover promises an unsupported source. Record the integration gap and agree a file-based or revised path.
Prepare the inputs
- sales_handover
- Required
Agreed outcomes and client scope
Separate promised deliverables from unresolved assumptions.
- source_systems
- Required
Systems, owners and permitted access
Keep client boundaries and credential handling explicit.
- integration_procedure
- Required
Versioned project path
Use maintained steps and supported connectors.
- data_contract
- Required
Schema, attribution and output requirements
Define required keys, timezones and validation examples.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check sales_handover, source_systems, integration_procedure, data_contract before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected sales_handover and any missing required fields.
Select the relevant project path and gather missing client inputs
- Select the relevant onboarding path and collect missing client facts before changing configuration.
- Reconcile sample and refresh counts, keys and reporting periods to the source.
Checkpoint: A saved intermediate result for: Select the relevant project path and gather missing client inputs.
Follow the linked integration and data-validation steps
- Follow the supported integration steps, testing a bounded sample for schema, identity joins and expected data coverage.
- Check the final output answers the agreed business requirement, not merely that the connector returns data.
Checkpoint: A saved intermediate result for: Follow the linked integration and data-validation steps.
Ask the responsible person to confirm schemas, attribution, and output requirements
- Have responsible owners confirm attribution, metric meaning and output requirements using actual sample rows.
- Reconcile sample and refresh counts, keys and reporting periods to the source.
Checkpoint: A saved intermediate result for: Ask the responsible person to confirm schemas, attribution, and output requirements.
Verify the resulting data flow and capture new edge cases in the procedure
- Run and observe a complete refresh, reconcile outputs with sources and record edge cases for a reviewed procedure update.
- Check the final output answers the agreed business requirement, not merely that the connector returns data.
Checkpoint: A saved intermediate result for: Verify the resulting data flow and capture new edge cases in the procedure.
Package the result and unresolved work
- Check actual data quality and refresh behavior. A completed setup step does not prove the full integration is reliable; preserve access boundaries across clients.
- Do not reuse another client’s data or credentials to fill an onboarding gap.
Checkpoint: A validated client integration and a maintained onboarding record. Unresolved items remain visible in the review record.
Decisions along the way
The handover promises an unsupported source.
Record the integration gap and agree a file-based or revised path.
Sample rows violate the expected schema.
Stop downstream assumptions and resolve field mapping with the source owner.
Setup succeeds but scheduled refresh fails.
Keep integration readiness incomplete and diagnose the refresh before handover.
What you will produce
guided-client-data-onboarding-result.json
JSONA validated client integration and a maintained onboarding record. Label proposed and completed states separately.
Include: project_id · procedure_version · source_mapping · schema_checks · refresh_receipt · reconciliation · readiness_gaps · status · evidence_reference · review_note
guided-client-data-onboarding-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving data_contract.
Include: source_reference · question · owner · next_action
Check the result
- Reconcile sample and refresh counts, keys and reporting periods to the source.
- Check the final output answers the agreed business requirement, not merely that the connector returns data.
- Inspect sales_handover and source_systems in both the original and output; confirm that record identity and interpretation survived the transformation.
- Check actual data quality and refresh behavior. A completed setup step does not prove the full integration is reliable; preserve access boundaries across clients.
When something goes wrong
The handover promises an unsupported source.
Record the integration gap and agree a file-based or revised path. Retain the affected evidence and recovery status.
Sample rows violate the expected schema.
Stop downstream assumptions and resolve field mapping with the source owner. Retain the affected evidence and recovery status.
Setup succeeds but scheduled refresh fails.
Keep integration readiness incomplete and diagnose the refresh before handover. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Guide a new client through data integration for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Project P-6 expects daily orders joined by customer_id. Sample export uses client_ref; one row lacks it. Connection credentials work.
Expected result
Synthetic expected result: Map client_ref only after owner confirmation, quarantine the missing-key row and verify a daily refresh. Working credentials alone do not mark onboarding complete.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure time to validated data readiness; unresolved schema or attribution issues at handoff.
Stop or revise
Setup succeeds but scheduled refresh fails. Pause affected records and apply this recovery: Keep integration readiness incomplete and diagnose the refresh before handover.
Keep the scope clear
- Do not reuse another client’s data or credentials to fill an onboarding gap.
- Configuration changes stay within the agreed integration scope; business definitions require owner confirmation.
Check before using
Check actual data quality and refresh behavior. A completed setup step does not prove the full integration is reliable; preserve access boundaries across clients.
Business activities
- Onboard customers, partners, and members
- Deliver recurring client work
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Sales handover · Project type and source systems · Maintained integration procedures
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow