n8n templates
Ten workflows to import into n8n with the Enroutia node: lead scoring, invoice extraction, keyword clusters, product pages, meeting summaries, brand reports, and the alerts and cost sheet that keep an automation business in order. Each one says what it asks for, what it tags and what a run costs.
Importing one
- Install the community node: Settings → Community Nodes → Install → n8n-nodes-enroutia. The Enroutia Chat Model, used inside the AI Agent, needs n8n 2.0 or later.
- Download the template below and use Workflows → Import from File, or paste the JSON onto the canvas.
- Open each node with a red credential and pick one. The templates name their credentials but carry none: the Enroutia one is an API key from the panel, one per client if you work for several.
- Nothing is read from the n8n environment, which n8n 2.0 blocks in nodes by default. The account token of the brand report and cost export templates goes in a Header Auth credential; the signed-webhook templates keep their secret in a Settings node after the trigger, shipped as REPLACE_WITH_YOUR_WEBHOOK_SECRET and refused until you replace it. A webhook or form has a public URL that spends your balance: the webhooks that run a model ship with Header Auth on, and each form's README says how to close it.
# Header Auth credential "Enroutia account token" (brand report, cost export)
Name: Authorization
Value: Bearer pat_live_…
# Settings node, right after the trigger (alias watch, alerts)
ENROUTIA_WEBHOOK_SECRET = whsec_… # ships as REPLACE_WITH_YOUR_WEBHOOK_SECRET
ENROUTIA_API = https://platform.enroutia.com
# n8n instance, for the signature check
NODE_FUNCTION_ALLOW_BUILTIN=cryptoThe ten
- Classify inbound leadsA webhook receives the lead; an AI Agent on the Enroutia Chat Model answers with category, score, reason and next step as fixed JSON.Per run: about €0.001Download
01-lead-classifier.json - Extract invoice fields to JSONInvoice text in, supplier, tax id, dates, totals and line items out, with guaranteed JSON: an invalid answer is retried once and billed once.Per run: about €0.002 for a one-page invoiceDownload
02-invoice-extraction.json - Cluster SEO keywordsEmbeddings group the keywords by meaning, then one short call names each cluster with its intent and pillar keyword. Scales to thousands of keywords.Per run: about €0.013 per 200 keywordsDownload
03-keyword-clustering.json - Product page from a formName and features in; title, descriptions, bullets and meta description out, with nothing invented that the features did not say.Per run: about €0.0013Download
04-product-description.json - Summarise a call or meetingA transcript in; summary, decisions, action items with owner and date, and open questions out, from an AI Agent with a structured output parser.Per run: about €0.005 for a 30-minute callDownload
05-meeting-summary.json - Brand report from a formA public form orders a report of what the AI models say about a brand, with an account token; the finished report arrives by signed webhook.Per run: the response's estimate, before anything runsDownload
06-brand-report-form.json - Alias watch to Slack and emailThe alias_check_degraded and alias_proposal webhooks, signature verified, as a Slack message and an email with the version to roll back to or the cheaper model found.Per run: €0Download
07-alias-watch-alerts.json - Idle workflow, spend anomaly and client budget alertsworkflow_idle, spend_anomaly and the two client budget webhooks, signature verified, as Slack messages that say which workflow or client and how much.Per run: €0Download
08-idle-workflow-and-anomaly-alerts.json - Daily cost per client to Google SheetsEvery morning, yesterday's usage export by key, one row per client key, in the same whole cents the panel shows.Per run: €0Download
09-cost-per-client-to-sheets.json - Compare three models and keep the bestCompare Models sends one prompt to three models in parallel; a judge call picks the best answer and keeps it with its model, latency and usage.Per run: about €0.0014Download
10-compare-three-models.json
What they tag
The Enroutia nodes tag every call with the workflow's id and name and the node's name on their own, which is what Usage by workflow, the idle-workflow webhook and the anomaly webhook run on. Templates that work for an end client pass the client tag from their input, so a client with a budget by tag is capped at the gateway.
Why some call enroutia/…
Tasks that deserve their own model call an alias you own, such as enroutia/leads or enroutia/invoices, so the model behind them changes from the panel and the workflow stays as it is. Create the alias in the panel; until then the name resolves to auto and the run still answers.
About the costs
Estimates at the catalogue price of the model named, with auto's price for aliases. The panel shows what each run actually cost, under the workflow that made it.
See also: Guide per tool · Tags and cost per automation · Aliases