Client Intake → Google Sheets CRM + Gmail Alert (Free Lite)
Analyzed
External call with no timeout configured — A single slow external call can block the entire workflow execution. At high trigger frequency, accumulated stuck executions can exhaust the n8n execution queue.
Side-effect node has no audit trail — If this action is disputed, replayed, or causes a data inconsistency, there is no structured record of what was sent, when, and with what data. Debugging requires cross-referencing n8n execution history with the external system's own logs.
| Check | Description | Status |
|---|---|---|
| Failure Alerting | Failures silent — only visible in execution log | Missing |
| Retry on Failure | Transient failures cause permanent stops | Present |
| Request Timeouts | Slow providers can block execution indefinitely | Missing |
| Duplicate Prevention | Retry on write events creates duplicate records | Missing |
| Empty Response Handling | Zero-result lookups break downstream logic | Present |
| AI Output Limits | Output cost and parsing risk unbounded | N/A |
| AI Output Format | Free-form output will break downstream parsers | N/A |
| Activity Logging | Side effects unlogged | Missing |
| Write Deduplication | Webhook replays may create duplicate records | Present |
Run this analysis on your own workflows
- Alert You: New Lead
A single slow external call can block the entire workflow execution. At high trigger frequency, accumulated stuck executions can exhaust the n8n execution queue.
Set a timeout under the node's Additional Options. A value of 10,000–30,000 ms (10–30 seconds) is a reasonable starting point for most APIs; adjust based on the provider's documented SLA.
- Alert You: New Lead
These expressions work reliably against test data where all fields are present. In production, fields may be absent, null, or differently typed — causing a runtime error or silent null propagation at the point of the expression.
- In `subject`, change {{ $("Normalize Client Data").item.json.name }} to {{ $("Normalize Client Data")?.item?.json?.name }}.
- In `message`, change {{ $("Normalize Client Data").item.json.name }} to {{ $("Normalize Client Data")?.item?.json?.name }}.
- Normalize Client Data
- Alert You: New Lead
Operators cannot tell from external signals that a run failed. Silent failures go undetected until a downstream system shows missing data or a user reports a problem.
Connect a dedicated Error Workflow in workflow settings, or add a per-node onError: "continueErrorOutput" path that sends an alert via Slack, email, or a logging service.
- Alert You: New Lead
If this action is disputed, replayed, or causes a data inconsistency, there is no structured record of what was sent, when, and with what data. Debugging requires cross-referencing n8n execution history with the external system's own logs.
After the write node, add a step that records the key fields of the action to a log — a Google Sheet row append, a database insert to an audit table, or a Slack message to a dedicated ops channel. Include: timestamp, action type, affected ID, and result.
| # | Issue title | Issue description | Affected nodes | |||
|---|---|---|---|---|---|---|
| 1 | Reliability | External call with no timeout configured | Node "Alert You: New Lead" makes an external call with no timeout parameter set. The n8n execution will wait indefinitely if the provider is slow or unresponsive. | Alert You: New Lead | High | 90% |
| 2 | Reliability | Fragile expression — likely to fail when production data shape differs from test data | Node "Alert You: New Lead" contains expression(s) with risky patterns that assume fields are always present. | Alert You: New Lead | High | 85% |
| 3 | Reliability | No error handler or failure notification path | Workflow has 2 high-risk nodes (external calls or writes) with no configured error workflow and no inline notification path. If a production execution fails, the failure only appears in execution history. | Normalize Client Data, Alert You: New Lead | High | 85% |
| 4 | Observability | Side-effect node has no audit trail | Node "Alert You: New Lead" performs a write node: "alert you: new lead" (sideeffect: external_write) operation with no logging or audit trail detected downstream. | Alert You: New Lead | Medium | 70% |