Skip to main content

Pull Square sales summary reports for automated reporting and analysis

Workflow preview

Workflow preview
100%
Pull Square sales summary reports for automated reporting and analysis preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Programatically Pull Square Report Data Into N8N What It Does This sub workflow connects to the Square API and generates a daily sales summary report for all of your Square locations. The report ma...

Best for

  • CRM automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.if, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.code, n8n-nodes-base.stickynote

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Pull Square sales summary reports for automated reporting and analysis
Workflow name
Pull Square sales summary reports for automated reporting and analysis

Programatically Pull Square Report Data Into N8N

What It Does

This sub-workflow connects to the Square API and generates a daily sales summary report for all of your Square locations. The report matches the figures displayed in the Square Dashboard > Reports > Sales Summary.

It’s designed to be reused in other workflows, ideal for reporting, data storage, accounting, or automation.

Prerequisites

To use this workflow, you'll need:

  • Square API credentials (configured as a Header Auth credential)

How to Set Up Square Credentials:

  • Go to Credentials > Create New
  • Choose Header Auth
  • Set the Name to "Authorization"
  • Set the Value to your Square Access Token (e.g., Bearer <your-api-key>)

How It Works

  1. Trigger: The workflow is triggered as a sub-workflow, requiring a report_date input.
  2. Fetch Locations: An HTTP request gets all Square locations linked to your account.
  3. Fetch Orders: For each location, an HTTP request pulls completed orders for the specified report_date.
  4. Filter Empty Locations: Locations with no sales are ignored.
  5. Aggregate Sales Data: A Code node processes the order data and produces a summary identical to Square’s built-in Sales Summary report.
  6. Output: A cleaned, consistent summary that can be consumed by parent workflows or other nodes.

Example Use Cases

  • Automatically store daily sales data in Google Sheets, MySQL, or PostgreSQL for analysis and historical tracking
  • Automatically send daily email or Slack reports to managers or finance teams
  • Build weekly/monthly reports by looping over multiple dates
  • Push sales data into accounting software like QuickBooks or Xero for automated bookkeeping
  • Calculate commissions or rent payments based on sales volume

How to Use

  • Configure both HTTP Request nodes to use your Square API credential.
  • If you are not in the Toronto/New York Timezone, please change the "start_at" and "end_at" parameters in the second HTTP node from "-05:00" to your local timezone
  • Use as a sub-workflow inside a main workflow.
  • Pass a report_date (formatted as YYYY-MM-DD) to the sub-workflow when you call it.

Customization Options

  • Add pagination to handle locations with more than 1,000 orders per day.
  • Expand the workflow to save or send the report output via additional integrations (email, database, webhook, etc.).

Why It's Useful

This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data—whether for operations, finance, or performance monitoring.

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 - Get Square Locations

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

Block 2 - Turn Locations Into List

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

Block 3 - Ignore Locations w/o Sales

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

Block 4 - Get Sales from Square

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

Block 5 - When Executed by Another Workflow

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

Block 6 - Compile Sales Reports

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

Block 7 - Sticky Note

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

Block 8 - Sticky Note1

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

Block 9 - Sticky Note2

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

Block 10 - Sticky Note3

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

Block 11 - Sticky Note4

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

Block 12 - Sticky Note5

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

3. Summary Table

Workflow Pull Square sales summary reports for automated reporting and analysis
Complexity intermediate
Nodes 12
Categories CRM
Author Rosh Ragel
Published 24 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6358/6358.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 Pull Square sales summary reports for automated reporting and analysis do?

Programatically Pull Square Report Data Into N8N What It Does This sub workflow connects to the Square API and generates a daily sales summary report for all of your Square locations. The report ma...

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 CRM use case.