n8n Workflow Templates: 3 Downloads and 7 Build Patterns

A useful n8n workflow template should give you something you can import, run, and inspect before connecting a customer system. These three downloads do that with synthetic records. No account credentials, mailing lists, or payment connections are included.

They are small working examples. The pipeline template builds a digest; it doesn't fetch Salesforce records. The invoice template checks a draft; it doesn't create or send an invoice. Inspect the output before adding your own integrations.

Download the n8n templates

Use and adapt the files under the MIT license. They use built-in Manual Trigger, Code, Sticky Note, and, for the alert formatter, Error Trigger nodes. Keep a copy of the version you test.

Verified on September 7, 2026: all three files imported and completed their sample path in n8n 2.37.10 using the CLI. Ten automated checks also cover invalid amounts, duplicate records, currency handling, and missing error fields. External services and notification delivery are not part of those tests.

Import and run a sample

1. Download a JSON file above. If your browser displays text, save it with its .json extension.
2. Create a workflow in a test n8n instance and choose Import from File from the workflow menu. You can also paste the copied JSON into the canvas. See n8n's import instructions.
3. Run the Run sample path, leaving Sample records connected.
4. Open the final Code node's output and compare it with the expected result below.
5. Duplicate the workflow before adapting it. Replace the sample-data node with your read step, preserve the input fields, and test exceptions before adding an outbound action.

The downloads contain no schedule, webhook, or external write node. Importing them doesn't start a customer process. A working sample doesn't establish that your permissions, volume, or business rules are correct.

1. Error alert formatter

Expected sample output: workflow Invoice validation demo, failed node Validate invoice, execution demo-104, and a message containing its example execution URL.

There are two entry points. Run sample supplies a synthetic event. Error Trigger accepts a failure from another workflow once you select this workflow in that workflow's error settings. Both feed the same formatter.

An error at a trigger can lack a saved execution ID or URL. The formatter handles that case and directs the operator to trigger and instance logs. It excludes raw error messages and stack traces, which can contain request bodies or credentials. Keep that detail inside the execution history.

To send the message, add a notification node after Format alert, configure credentials in n8n, and map text. A manual run of a failing workflow won't exercise the automatic Error Trigger path; test that separately with a harmless scheduled failure in a test environment. n8n Error Trigger documentation.

An alert cannot detect an event that never arrived. Reconcile expected inputs against completed outcomes as well. Our error-handling patterns explain the difference.

2. Pipeline digest

Expected sample output: three included opportunities. Closed Won has one USD deal worth $2,500. Proposal has one USD deal worth $1,750 and one EUR deal worth €900. Currencies remain separate.

The input contains windowStart, windowEnd, and an opportunities array. Records need an ID, stage, currency, integer amount in minor units, and update timestamp. The example accepts USD, EUR, and GBP, each with two decimal places. Extend currency handling deliberately for other currencies.

The interval includes its start and excludes its end. Duplicate IDs within the interval resolve to the latest timestamp. Malformed rows appear in invalidIds; an empty interval produces an explicit message.

This summarizes updated opportunity snapshots. It cannot reconstruct every stage transition between extracts. Use change history or stored events when the question is movement through the funnel.

For a live digest, replace the sample with a paginated CRM query over a defined interval, retain a watermark, and choose what happens when the query fails. Never report an API failure as “no deals.” Add delivery after those cases are visible to the operator.

3. Invoice review gate

The invoice-review implementation note includes downloadable fixtures, complete expected outputs, and a standalone verification command. It also demonstrates why the batch duplicate check does not prevent a repeat across executions.

Expected sample output: D-104 is ready_for_review, with a $2,500 draft. D-105 is needs_review: its lines total $1,700 against an approved $1,750. The rejected record has no draft.

The example accepts positive USD invoice totals in integer cents. It checks deal and customer references, commercial approval, billing version, descriptions, quantities, and arithmetic. A duplicate deal/version in the same batch sends both records to review.

Branch downstream nodes on status. Only ready_for_review contains a draft; route needs_review to a named person with its reasons. Tax, credits, discounts, currency conversion, and partial invoicing are outside this example. Add explicit rules before using it for billing.

The source key identifies a deal and billing version. It doesn't prevent duplicates across executions. Before adding invoice creation, persist source-to-invoice references, reconcile uncertain API responses, and use the provider's supported idempotency controls. A retry after a timeout must not create a second invoice.

Evaluate Stripe's native Salesforce app before choosing middleware for Salesforce billing. Our invoicing walkthrough covers the wider handoff.

Seven more workflow patterns

These are architecture patterns, not additional JSON downloads.

4. Contract extraction into a review queue

A signed document arrives and an AI step proposes structured terms. Validate required fields, preserve the source reference, and route uncertain values to a reviewer before updating commercial records. A response that parses as JSON can still contain the wrong payment term.

5. Lead routing with capacity rules

Resolve territory, owner availability, and a fallback before assigning the lead. If concurrent runs share a round-robin counter, use a transactional store or serialized assignment process. A spreadsheet cell is not an atomic lock. Escalate unaccepted assignments after an agreed deadline.

6. Booking to CRM handoff

Find the correct contact and record the meeting. Deduplicate with the scheduling provider's event ID and handle cancellations and reschedules as updates. A booking isn't automatically a qualified opportunity; define which meetings create one.

7. Enrichment with an exception route

Validate the inbound record, call your licensed enrichment source, and record where each added field came from. Preserve human-entered values according to ownership rules. Route ambiguous matches to review rather than attaching another company's data.

8. Invoice reminder eligibility

Find overdue invoices and check payment state again immediately before sending. Define holds for disputes and promises to pay. AI can draft wording for review; whether a customer should receive a payment demand needs an explicit business rule.

9. Customer onboarding cascade

An approved deal creates a project, folder, and delivery handoff. Store every created object's ID against the source deal so a retry resumes incomplete work. A partial failure should identify what succeeded and who owns the remaining exception.

10. HubSpot and Salesforce synchronization

Define field ownership before adding two-way writes. Store persistent IDs, change versions, and reconciliation results. Timestamps alone don't settle conflicting edits reliably. Start with a limited field set that both teams can explain.

Choose the first workflow by its failure cost

Start with a read-only digest when learning the runtime. Inspect its output, add an alert path, and test a validation gate before connecting a billing action.

Measure volume, manual handling time, exceptions, and review effort before estimating savings. The ROI calculator models your assumptions; the cost benchmark explains our published build estimates.

Our n8n consulting and development covers the permissions, history, retries, and ongoing operation around a workflow. Bring the sample and the case that fails. That's enough to begin a useful scoping conversation.