Block 1 - MySQL
- Type / Role
- n8n-nodes-base.mySql - mySql
- Config choices
- Version 2.4
This workflow is provided as-is. Please review and test before using in production.
Automated Weekly Project Cost Reports with MySQL and Outlook HTML Emails Use Case Need to keep your finance or operations team updated on missing project costs? This practical automated report w...
n8n-nodes-base.mysql, n8n-nodes-base.scheduletrigger, n8n-nodes-base.switch, n8n-nodes-base.microsoftoutlook
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Amjid Ali.
Original n8n.io sourceNeed to keep your finance or operations team updated on missing project costs?
This practical automated report workflow does the job without AI β and saves hours weekly.
budgeted_project_cost IS NULLbudgeted_project_costcost_center (e.g., Retail, Service, Projects){{ $json.project_name }}MySQL Setup:
SELECT project_name, cost_center FROM tabProject
WHERE status = 'Open' AND project_type = 'External' AND budgeted_project_cost IS NULL;
Outlook Configuration:
Send Email - Retail, Send Email - Service).Switch Node:
'Retail', 'Service', 'Projects').HTML Email Formatting:
<h3>Missing Budgeted Cost Report</h3>
<ul>
<li>Project: {{ $json.project_name }}</li>
<li>Cost Center: {{ $json.cost_center }}</li>
</ul>
Recipients:
[email protected] with the actual email addresses of the concerned teams.π Why Simple Workflows Work
π₯ Watch the video walkthrough:
https://youtube.com/@syncbricks
Amjid Ali
π amjidali.com
π n8n Book
π Learn n8n
> βStart simple, scale smart. Even basic workflows like this can save your team hours!β β Amjid Ali
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 | Automated weekly project cost reports with MySQL and Outlook HTML emails |
|---|---|
| Complexity | intermediate |
| Nodes | 6 |
| Categories | Document Extraction |
| Author | Amjid Ali |
| Published | 07 Apr 2025 |
Use the JSON export at /data/workflows/3453/3453.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.
Automated Weekly Project Cost Reports with MySQL and Outlook HTML Emails Use Case Need to keep your finance or operations team updated on missing project costs? This practical automated report w...
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 Document Extraction use case.