Skip to main content

Fetch Telr payment reports to SQL and send daily email summaries

Workflow preview

Workflow preview
100%
Fetch Telr payment reports to SQL and send daily email summaries preview
Open on n8n.io

1. Workflow Overview

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 A...

Best for

  • Document Extraction automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.set, n8n-nodes-base.compression, n8n-nodes-base.extractfromfile, n8n-nodes-base.code, n8n-nodes-base.scheduletrigger, n8n-nodes-base.emailsend, n8n-nodes-base.httprequest, n8n-nodes-base.xml

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mohamed Abubakkar.

Original n8n.io source

1.1 Workflow description

Title
Fetch Telr payment reports to SQL and send daily email summaries
Workflow name
Fetch Telr payment reports to SQL and send daily email summaries
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), decompresses and extracts data from an XLS file, transforms it with JavaScript, inserts it into a SQL database, and sends a success email notification.

Who it's for

Merchants, developers, and finance analysts using the Telr payment gateway who want to automate transaction report collection, transform the raw XLS data, persist it to a database, and receive automated email confirmations — all without manual intervention.

How it works:
  1. Schedule Trigger fires the workflow at your defined interval.

  2. Telr API fetches the raw transaction report.

  3. XML is converted to JSON for processing.

  4. Logic for Date calculates the relevant date range.

  5. Edit Fields maps and renames fields manually.

  6. Telr API with Date refetches with the computed date filter.

  7. Compression node decompresses the downloaded file.

  8. Extract from File reads the XLS content.

  9. Data Formation shapes the records for SQL.

  10. Code in JavaScript3 applies custom business logic.

  11. Data Insert SQL writes records to your database.

  12. Success Condition checks if the insert succeeded.

  13. Send Email dispatches a success notification.

Setup requirements

• Telr API credentials — add your Telr store ID and API key as n8n credentials (HTTP Header Auth). • Database credentials — configure a MySQL or PostgreSQL credential and update the table name in the SQL node. • Email credentials — set up SMTP or Gmail credentials for the Send Email node. • Schedule — adjust the cron expression in the Schedule Trigger to match your reporting frequency. • JavaScript node — review the Code in JavaScript3 node and adapt any field names or business logic to match your Telr account's XLS format.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Edit Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 2 - Compression

Type / Role
n8n-nodes-base.compression - compression
Config choices
Version 1.1

Block 3 - Extract from File

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 4 - Code in JavaScript3

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 5 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.3

Block 6 - Send email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 7 - TELR API

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 8 - Convert XML to JSON

Type / Role
n8n-nodes-base.xml - xml
Config choices
Version 1

Block 9 - Logic for date

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - TELR API WITH DATE

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 11 - Data Formation

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - Data Insert SQL

Type / Role
n8n-nodes-base.microsoftSql - microsoftSql
Config choices
Version 1.1

Block 13 - Success Condition

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 14 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Fetch Telr payment reports to SQL and send daily email summaries
Complexity advanced
Nodes 18
Categories Document Extraction
Author Mohamed Abubakkar
Published 22 Apr 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15222/15222.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Fetch Telr payment reports to SQL and send daily email summaries do?

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 A...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.