Integration guide
n8n
Plan a scheduled review-output workflow.
Workflow deployment and configuration need to be agreed; no scheduled customer workflow is established here. Confirm the owner, permissions and a real acceptance test before relying on a connection.
Start with a retail decision
Choose the review
Plan a weekly reviewed-output delivery with an explicit destination and failure contact.
Make the evidence comparable
Inspect credentials references, schedule, duplicate handling and a test run before activation.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
Output scope to review: Configured workflow asset and a future reviewed-output test delivery
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Approved input resource · workflow template · destination · schedule · retry owner | Deliver an agreed output | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
Workflow deployment and configuration need to be agreed; no scheduled customer workflow is established here.
Do not send passwords, API keys or customer records through the contact form.