exploreAIExplore
How to Use n8n for Scheduled reporting and sync jobs
Learn n8n scheduled reporting and sync jobs with step by step workflows, realistic examples, and verified plan notes.
This scheduled reporting and sync jobs guide shows a practical n8n path from brief to reviewable output. Lead with dead letter sheet, use respond 200, and keep AI bounded secondary until the core result is right. Plans: n8n.io/pricing. Explore: /explore/n8n.
Below is a full scheduled reporting and sync jobs walkthrough. See also /blog/how-to-use-n8n-for-multi-app-integration-pipelines, /blog/how-to-use-n8n-for-ai-steps-inside-workflows-llm-nodes, /blog/how-to-use-n8n-for-error-handling-retries-and-alerts.
When this workflow is the right job
Pick scheduled reporting and sync jobs for a focused n8n pass. Skip it when webhook-driven automations or multi-app integration pipelines covers the requirement more directly.
Step by step workflow
1. Brief Scheduled reporting and sync jobs
Write what must stay true for scheduled reporting and sync jobs in n8n before settings or spend.
Brief: Scheduled reporting and sync jobs Keep: Salesforce create from SOURCE Avoid: invented pricing or features Success: one reviewable output
2. Open n8n for Scheduled reporting and sync jobs
Use the n8n surface that owns scheduled reporting and sync jobs. Do not mix a neighboring workflow in the same pass.
Surface: Scheduled reporting and sync jobs Start: retry twice Plans: n8n.io/pricing
3. Pilot Scheduled reporting and sync jobs
Run a single scheduled reporting and sync jobs pilot. Score clarity, grounding, and whether ops durable still matches.
Pilot: Scheduled reporting and sync jobs [ ] SOURCE facts match [ ] execution URL clear [ ] Settings logged
4. Refine Scheduled reporting and sync jobs
Change one scheduled reporting and sync jobs dimension only. Save a template with variables for Notion deal won.
Refine: Scheduled reporting and sync jobs Change: LLM JSON parse Keep: SOURCE and self hosted
Practical scheduled reporting and sync jobs examples
Salesforce create
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Salesforce create" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Salesforce create" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Salesforce create - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Salesforce create) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Salesforce create, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
Postgres row
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Postgres row" that produces a readable ops summary in #sales. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Postgres row" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Postgres row - Notification destination #sales Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Postgres row) → Notification Error branch → Dead-letter + alert #sales Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Postgres row, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
S3 upload
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "S3 upload" that produces a readable ops summary in #support-alerts. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "S3 upload" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to S3 upload - Notification destination #support-alerts Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (S3 upload) → Notification Error branch → Dead-letter + alert #support-alerts Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for S3 upload, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
cron London
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "cron London" that produces a readable ops summary in #data-ops. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "cron London" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to cron London - Notification destination #data-ops Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (cron London) → Notification Error branch → Dead-letter + alert #data-ops Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for cron London, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
dead letter sheet
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "dead letter sheet" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "dead letter sheet" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to dead letter sheet - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (dead letter sheet) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for dead letter sheet, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
auth header
Scenario: Ops needs a n8n automation for scheduled reporting and sync jobs focused on "auth header". External callers must authenticate; duplicate events must not create duplicate records. Objective: Accept a validated event for scheduled reporting and sync jobs, enforce idempotency around "auth header", route or write downstream, and acknowledge quickly. Inputs: - Shared secret or signature header - JSON payload with required keys for auth header - Destination credentials from the credential store - Notification channel #sales for failures Workflow: Webhook → Validate auth/schema → Dedupe on stable key → auth header action → Respond 200 Error branch → Alert #sales with execution id Requirements: - Reject missing auth with 401 and do not process the body. - Keep credentials in the platform credential store. - Handle empty or already-seen payloads without failing the workflow. - Never hardcode secrets in expression fields. Expected output: A compact ack with processed/rejected status, destination id when written, and a clear failure alert if auth header cannot complete.
rate limit wait
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "rate limit wait" that produces a readable ops summary in #support-alerts. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "rate limit wait" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to rate limit wait - Notification destination #support-alerts Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (rate limit wait) → Notification Error branch → Dead-letter + alert #support-alerts Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for rate limit wait, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
execution URL
Scenario: Ops needs a n8n automation for scheduled reporting and sync jobs focused on "execution URL". External callers must authenticate; duplicate events must not create duplicate records. Objective: Accept a validated event for scheduled reporting and sync jobs, enforce idempotency around "execution URL", route or write downstream, and acknowledge quickly. Inputs: - Shared secret or signature header - JSON payload with required keys for execution URL - Destination credentials from the credential store - Notification channel #data-ops for failures Workflow: Webhook → Validate auth/schema → Dedupe on stable key → execution URL action → Respond 200 Error branch → Alert #data-ops with execution id Requirements: - Reject missing auth with 401 and do not process the body. - Keep credentials in the platform credential store. - Handle empty or already-seen payloads without failing the workflow. - Never hardcode secrets in expression fields. Expected output: A compact ack with processed/rejected status, destination id when written, and a clear failure alert if execution URL cannot complete.
idempotent session
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "idempotent session" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "idempotent session" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to idempotent session - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (idempotent session) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for idempotent session, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
new lead webhook
Scenario: Ops needs a n8n automation for scheduled reporting and sync jobs focused on "new lead webhook". External callers must authenticate; duplicate events must not create duplicate records. Objective: Accept a validated event for scheduled reporting and sync jobs, enforce idempotency around "new lead webhook", route or write downstream, and acknowledge quickly. Inputs: - Shared secret or signature header - JSON payload with required keys for new lead webhook - Destination credentials from the credential store - Notification channel #sales for failures Workflow: Webhook → Validate auth/schema → Dedupe on stable key → new lead webhook action → Respond 200 Error branch → Alert #sales with execution id Requirements: - Reject missing auth with 401 and do not process the body. - Keep credentials in the platform credential store. - Handle empty or already-seen payloads without failing the workflow. - Never hardcode secrets in expression fields. Expected output: A compact ack with processed/rejected status, destination id when written, and a clear failure alert if new lead webhook cannot complete.
Stripe charge sync
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Stripe charge sync" that produces a readable ops summary in #support-alerts. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Stripe charge sync" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Stripe charge sync - Notification destination #support-alerts Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Stripe charge sync) → Notification Error branch → Dead-letter + alert #support-alerts Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Stripe charge sync, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
Notion deal won
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Notion deal won" that produces a readable ops summary in #data-ops. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Notion deal won" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Notion deal won - Notification destination #data-ops Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Notion deal won) → Notification Error branch → Dead-letter + alert #data-ops Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Notion deal won, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
support ticket LLM
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "support ticket LLM" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "support ticket LLM" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to support ticket LLM - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (support ticket LLM) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for support ticket LLM, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
invoice error alert
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "invoice error alert" that produces a readable ops summary in #sales. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "invoice error alert" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to invoice error alert - Notification destination #sales Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (invoice error alert) → Notification Error branch → Dead-letter + alert #sales Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for invoice error alert, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
self host backup
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "self host backup" that produces a readable ops summary in #support-alerts. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "self host backup" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to self host backup - Notification destination #support-alerts Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (self host backup) → Notification Error branch → Dead-letter + alert #support-alerts Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for self host backup, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
report webhook
Scenario: Ops needs a n8n automation for scheduled reporting and sync jobs focused on "report webhook". External callers must authenticate; duplicate events must not create duplicate records. Objective: Accept a validated event for scheduled reporting and sync jobs, enforce idempotency around "report webhook", route or write downstream, and acknowledge quickly. Inputs: - Shared secret or signature header - JSON payload with required keys for report webhook - Destination credentials from the credential store - Notification channel #data-ops for failures Workflow: Webhook → Validate auth/schema → Dedupe on stable key → report webhook action → Respond 200 Error branch → Alert #data-ops with execution id Requirements: - Reject missing auth with 401 and do not process the body. - Keep credentials in the platform credential store. - Handle empty or already-seen payloads without failing the workflow. - Never hardcode secrets in expression fields. Expected output: A compact ack with processed/rejected status, destination id when written, and a clear failure alert if report webhook cannot complete.
AI Assistant draft
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "AI Assistant draft" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "AI Assistant draft" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to AI Assistant draft - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (AI Assistant draft) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for AI Assistant draft, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
Sheets append
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Sheets append" that produces a readable ops summary in #sales. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Sheets append" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Sheets append - Notification destination #sales Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Sheets append) → Notification Error branch → Dead-letter + alert #sales Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Sheets append, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
Slack ops ping
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Slack ops ping" that produces a readable ops summary in #support-alerts. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Slack ops ping" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Slack ops ping - Notification destination #support-alerts Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Slack ops ping) → Notification Error branch → Dead-letter + alert #support-alerts Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Slack ops ping, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
HubSpot dedupe
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "HubSpot dedupe" that produces a readable ops summary in #data-ops. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "HubSpot dedupe" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to HubSpot dedupe - Notification destination #data-ops Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (HubSpot dedupe) → Notification Error branch → Dead-letter + alert #data-ops Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for HubSpot dedupe, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
Mailchimp branch
Scenario: A team needs a n8n scheduled reporting and sync jobs job centered on "Mailchimp branch" that produces a readable ops summary in #operations. Objective: Fetch or process the relevant records for scheduled reporting and sync jobs, apply "Mailchimp branch" correctly, calculate reviewable totals, and notify without inventing fields. Inputs: - Source/destination credentials from the credential store - Date window (prefer previous day computed automatically when daily) - Filters tied to Mailchimp branch - Notification destination #operations Workflow: Schedule Trigger → Fetch/Source → Filter → Transform (Mailchimp branch) → Notification Error branch → Dead-letter + alert #operations Requirements: - Use the previous day's date automatically when the job is daily. - Handle an empty result without failing; send a clear zero-result note. - Add an error branch for failed upstream requests including execution id. - Keep credentials in the platform credential store. Expected output: A report covering counts, key breakdowns for Mailchimp branch, and a clear failure message if the scheduled reporting and sync jobs workflow cannot complete.
How to improve scheduled reporting and sync jobs
Make scheduled reporting and sync jobs easier to review by labeling Postgres row fields that must never change in n8n.
Speed scheduled reporting and sync jobs iteration by cloning the last good n8n run and altering only retry twice.
Stabilize scheduled reporting and sync jobs by pinning idempotent after cron London is approved in n8n.
Reduce scheduled reporting and sync jobs rework by rejecting drafts that invent claims about dead letter sheet in n8n.
Improve scheduled reporting and sync jobs handoffs by recording which n8n control produced the auth header result.
Strengthen scheduled reporting and sync jobs by adding a second reader who only checks rate limit wait spelling and facts in n8n.
Lift scheduled reporting and sync jobs consistency by reusing the same Schedule trigger vocabulary across related n8n jobs.
Harden scheduled reporting and sync jobs by testing an empty or incomplete idempotent session input before trusting n8n defaults.
Prompting and usage guidance
Lead scheduled reporting and sync jobs with constraints: channel, length, and forbidden claims inside n8n.
Separate creative instructions from SOURCE so scheduled reporting and sync jobs stays grounded in n8n.
Request scheduled reporting and sync jobs output as a checklist first when stakeholders need approval gates.
For scheduled reporting and sync jobs, describe cron London with concrete nouns, then add cloud billed only if the draft already works.
Ask n8n to list assumptions made during scheduled reporting and sync jobs before you accept the draft.
Limitations to respect
Do not invent credit costs for scheduled reporting and sync jobs; read live numbers on n8n.io/pricing.
n8n can be wrong. Treat scheduled reporting and sync jobs as provisional until review.
Connected apps used in scheduled reporting and sync jobs may throttle traffic independently of n8n.
If documentation is silent on a scheduled reporting and sync jobs claim, leave it out rather than guessing.
Practical tips for this workflow
Document n8n UI labels used for scheduled reporting and sync jobs so handoffs about Notion deal won do not rely on memory.
Store winning scheduled reporting and sync jobs settings as a template with variables only for Slack ops ping fields in n8n.
Approve SOURCE facts before spending budget on scheduled reporting and sync jobs variants that mention dead letter sheet in n8n.
Pair customer facing scheduled reporting and sync jobs exports with a human read that checks invented claims about Notion deal won.
Log n8n run identifiers for scheduled reporting and sync jobs so ops can replay Set map fields failures without guessing.
Split oversized scheduled reporting and sync jobs work into smaller activate after test passes rather than one overloaded n8n request.
Review scheduled reporting and sync jobs while context is fresh; delayed checks miss alert rich mismatches on Notion deal won.
If scheduled reporting and sync jobs touches compliance language about Slack ops ping, lock verbatim strings outside n8n first.
Retire scheduled reporting and sync jobs templates when n8n docs change names or gates for dead letter sheet workflows.
For scheduled reporting and sync jobs, capture a before and after artifact of Notion deal won every time n8n settings change.
Common mistakes
- Starting scheduled reporting and sync jobs without SOURCE facts in n8n
- Treating marketing blogs as official n8n limits
- Regenerating everything when one scheduled reporting and sync jobs section failed
- Leaving credentials in scheduled reporting and sync jobs node fields instead of vaults
- Promising delivery dates before checking n8n plan access
- Skipping the human read on customer facing scheduled reporting and sync jobs drafts
After this scheduled reporting and sync jobs guide, continue with /blog/how-to-use-n8n-for-multi-app-integration-pipelines, /blog/how-to-use-n8n-for-ai-steps-inside-workflows-llm-nodes, /blog/how-to-use-n8n-for-error-handling-retries-and-alerts. Start again at /explore/n8n if you need the full n8n map.