Fetch Telr payment reports to SQL and send daily email summaries
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 13 nodes and runs on a schedule (every day at 09:00). Along the way it connects Microsoft SQL. It also calls secure.telr.com over HTTP.
How it runs
Trigger: On a schedule (every day at 09:00).
- TELR API (HTTP Request): calls secure.telr.com
- Convert XML to JSON (XML): converts between XML and JSON
- Logic for date (Code): runs custom JavaScript code
- Edit Fields (Edit Fields (Set)): sets 1 field: Link
- TELR API WITH DATE (HTTP Request): calls an HTTP API
- Compression: uses Compression
- Extract from File: extracts data from a file (xls)
- Data Formation (Code): runs custom JavaScript code
- Code: runs custom JavaScript code
- Data Insert SQL (Microsoft SQL): run a query
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: secure.telr.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Edit Fields (Set)
n8n-nodes-base.set - Compression
n8n-nodes-base.compression - Extract from File
n8n-nodes-base.extractFromFile - Code
n8n-nodes-base.code - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Send Email
n8n-nodes-base.emailSend - HTTP Request
n8n-nodes-base.httpRequest - XML
n8n-nodes-base.xml - Microsoft SQL
n8n-nodes-base.microsoftSql - If
n8n-nodes-base.if
From the author
Description This workflow automates the full cycle of fetching, processing, and storing Telr payment gateway reports — and then notifying your team by email. It runs on a schedule, calls the Telr API twice (once for the raw file, once filtered by date),…