Client runbook

Lead routing — client runbook

Lead routing

Prepared byNorthline Automation Studio
ClientAcme Studio (synthetic example)
Date2026-09-21

4 nodes · 3 connections · 2 credential types

Review before sharing: workflow and node names, node types and your manual notes can contain client or business information. Rename or edit sensitive labels in the source before generating a shared copy. Never enter passwords, tokens or other secrets in this runbook.

This document lists exported workflow structure and your manual runbook notes. Parameter values, credential names and IDs, workflow notes, pinned data and execution data are excluded. It does not validate behavior, inspect configuration values for safety, run the workflow, or verify credential access.

Runbook

Purpose and scope

Record each submitted lead in the team's spreadsheet and notify the sales channel.

Owner and escalation

Example only: assign a real workflow owner and backup contact before delivery.

Setup and credentials

Connect client-owned Google Sheets and Slack credentials. Confirm the intended spreadsheet and sales channel inside n8n.

Operating instructions

Review the n8n execution list and confirm each test lead is written once. Before changing the workflow, export a backup and check the intended destination in each integration.

Recovery and rollback

Review the failed execution in n8n. Check whether the row was already written before retrying, so you do not create a duplicate lead.

Acceptance checks

Submit one clearly marked test lead. Confirm that exactly one row and one Slack notification are created. Remove the test record afterwards. This is an illustrative checklist; these tests have not been executed.

Additional notes

Synthetic example for reviewing the handoff format. This JSON structure is not a complete or tested production automation.

Node inventory

NodeType / versionStateCredential types
New leadn8n-nodes-base.webhook · v2EnabledNone declared
Clean fieldsn8n-nodes-base.set · v3.4EnabledNone declared
Save leadn8n-nodes-base.googleSheets · v4.6EnabledgoogleSheetsOAuth2Api
Notify teamn8n-nodes-base.slack · v2.3EnabledslackOAuth2Api

Credential dependencies

Only credential types declared on nodes are listed. Configure credentials in n8n and verify scopes and access separately. Missing declarations do not prove that no credentials are needed.

Connections

Exported links with zero-based output and input port indices. A question mark means the input index is unknown. This is not an execution trace.

FromToChannel / ports
New leadClean fieldsmain
output 0 → input 0
Clean fieldsSave leadmain
output 0 → input 0
Save leadNotify teammain
output 0 → input 0

Review warnings

No structural warnings were generated. Configuration and behavior still require review.

Version comparison

Comparison covers listed node metadata, configuration-change flags, named connections and their output/input port indices. Workflow name, settings and activation changes are flagged without showing values. Parameter values, canvas positions, pinned data and runtime state are omitted. A clean comparison does not prove identical execution behavior. Nodes match by ID, or by name when no ID exists.

Workflow changes (0)

None.

Nodes added (1)

Nodes removed (0)

None.

Nodes changed (0)

None.

Connections added (1)

Connections removed (0)

None.