Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Quick Overview This workflow runs daily at 10am, reads a marketplaces configuration file, fetches KPI statistics from marketplace APIs via HTTP requests, compiles the results into an Excel file, th...
n8n-nodes-base.stickynote, n8n-nodes-base.microsoftoutlook, n8n-nodes-base.set, n8n-nodes-base.readwritefile, n8n-nodes-base.splitout, n8n-nodes-base.splitinbatches, n8n-nodes-base.scheduletrigger, n8n-nodes-base.slack
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Eric Rigollet.
Original n8n.io sourceThis workflow runs daily at 10am, reads a marketplaces configuration file, fetches KPI statistics from marketplace APIs via HTTP requests, compiles the results into an Excel file, then posts a Slack notification and emails the file using Microsoft Outlook while also saving it to disk.
/home/node/.n8n-files/config/marketplaces.json from disk and parses it as JSON to get the list of marketplaces to process..xlsx file and attaches it to a Microsoft Outlook email./home/node/.n8n-files/share_files/.marketplaces.json file at /home/node/.n8n-files/config/marketplaces.json with a data array containing each marketplace’s marketplace name plus the baseUrlEnv, endpointstatsEnv, and apiKeyEnv environment-variable keys used to build the request.Authorization header)./home/node/.n8n-files/share_files/ if you want to save the generated Excel file.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.
| Workflow | Send daily marketplace KPI reports via Slack and Microsoft Outlook |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Market Research |
| Author | Eric Rigollet |
| Published | 10 Jun 2026 |
Use the JSON export at /data/workflows/16248/16248.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Quick Overview This workflow runs daily at 10am, reads a marketplaces configuration file, fetches KPI statistics from marketplace APIs via HTTP requests, compiles the results into an Excel file, th...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Market Research use case.