---
name: implement-evidence-controlled-crm-n8n-lead-routing
description: 'Implement an approved lead-routing contract across CRM sandbox configuration and disabled n8n staging orchestration, with synthetic reconciliation, retry evidence, and recovery controls. Use when when approved lead rules must be implemented across CRM and n8n in non-production; when an existing flow needs a controlled implementation/retest; when owners require evidence for consent, routing, SLA, retry, and disablement behavior.'
compatibility: 'Instruction-only Agent Skill. Requires an Agent Skills-compatible client and access to the tools or systems named in the instructions. No executable scripts are bundled.'
metadata:
  publisher: RichlyAI
  product: Amo.ng
  amo_id: AMO-S-000038
  canonical_url: 'https://amo.ng/skills/implement-evidence-controlled-crm-n8n-lead-routing'
  package_version: 1.0.0
  source_type: workflow
  source_amo_id: AMO-W-000033
  source_content_sha256: bf3ed1fa4be2697af0dbca32462f5b44502aec69e9149f6c81b90ebc4bfd3a7f
---

# Implement Evidence-Controlled CRM and n8n Lead Routing

## When to use this Skill

- When approved lead rules must be implemented across CRM and n8n in non-production; when an existing flow needs a controlled implementation/retest; when owners require evidence for consent, routing, SLA, retry, and disablement behavior.

## When not to use this Skill

- Without an authorized sandbox or editable export; to design rules from scratch; to use real leads or credentials; to send messages; to activate production; or to replay production events.

## Required inputs

- Owner-approved capture, consent, attribution, qualification, territory, routing, fallback, and SLA rules
- Source/CRM schemas plus an approved n8n blueprint and connector contracts
- Authorized CRM sandbox and n8n staging access or editable disabled exports
- Synthetic lead scenarios, expected outcomes, retry/replay constraints, and reconciliation evidence
- Allowed changes, test sinks, operational owners, activation authority, and rollback requirements

Use [INPUT-TEMPLATE.md](assets/INPUT-TEMPLATE.md) to organize the supplied information.

## Required tools or access

Published source tool designations: ChatGPT, Codex. These are source designations, not portable-client compatibility claims. Use only authorized access described in the inputs and source instructions. Do not claim access or inspection without evidence.

## Procedure

Before starting, read [SOURCE.md](references/SOURCE.md), including the exact Prompt instructions and any ordered Workflow steps, review notes and carry-forward requirements.

Use W33 in order. Reconcile the current routing/SLA contract, approve the n8n node/data design, implement CRM-side validation/deduplication/routing in sandbox, implement n8n orchestration in staging, and test failure/retry/replay safety. Preserve prior exports, use synthetic records and test sinks, record all side effects, reconcile source, CRM, and n8n outcomes, and prepare disablement and rollback evidence.

Published expected output:

A routing/SLA contract, CRM and n8n configuration manifests, field and decision mapping, synthetic execution/reconciliation ledger, retry and uncertain-completion matrix, disabled activation evidence, recovery runbook, and owner handoff.

## Review gates

Read and apply the source review instructions in [SOURCE.md](references/SOURCE.md) before acting. Keep proposed, unrun and executed actions distinct; preserve missing evidence and obtain the human approvals required by the source.

- Step 1: Stop if routing ownership, SLA timing, consent, or source attribution cannot be authorized; accountable owners must approve the correction priorities and routing/SLA contract before Step 2.
- Step 2: Stop if connectors, schemas, authority, or consequential action approval is undefined; do not proceed to sandbox implementation until the CRM and automation owners approve the contract.
- Step 3: Stop if no authorized sandbox/export exists, or if real leads, production ownership, credentials, or activation are requested.
- Step 4: Stop if staging/editable export is absent, secrets/live credentials are needed, or production effects cannot be disabled.
- Step 5: Keep activation disabled if uncertain completion, duplicate side effects, credentials, recovery, or alert ownership is unresolved.

## Completion criteria

Complete when every approved rule traces through CRM and n8n configuration to an observed synthetic test; consent, duplicates, invalid data, owner absence, SLA boundaries, connector failure, retry exhaustion, and uncertain completion are accounted for; source/CRM/n8n records reconcile; production triggers and messages remain disabled; and RevOps, privacy, platform, and release owners receive rollback and activation-gate evidence.

Use the [completion checklist](references/COMPLETION-CHECKLIST.md) and record unresolved items.

## Limitations

Never request secret values, alter real leads or production ownership, infer consent, send customer-visible messages, broaden connector authority, or claim activation/safety from unexecuted tests.

This is an instruction-only package. Packaging does not execute work, grant access or independently verify the package. Existing public verification in amo.json describes only the identified published source resources.

## References

- [Published source instructions](references/SOURCE.md)
- [Completion checklist](references/COMPLETION-CHECKLIST.md)
- [Input template](assets/INPUT-TEMPLATE.md)
- [Rights](RIGHTS.md)
- [Canonical Amo.ng Skill](https://amo.ng/skills/implement-evidence-controlled-crm-n8n-lead-routing)