We are a small professional collective looking for an experienced n8n developer to build two automated weekly email workflows against an existing PostgreSQL database.
What already exists:
A self-hosted n8n instance
A working data ingestion workflow that writes session records to PostgreSQL
Azure Communication Services connected to n8n for outbound email
What needs to be built:
A weekly workflow that queries the database, groups records into pairs, and sends formatted email statements to two parties with a third in copy
A second weekly workflow that queries the same database, groups records by recipient, and sends formatted email statements to external recipients with two parties in copy
A month-end summary version of both
Skills required:
Comfortable writing JavaScript in n8n’s Code node
Experience with PostgreSQL queries inside n8n
Experience sending formatted email via a third-party mail service from n8n
Project size: Small. Estimated 5 to 9 hours of work.
Budget: Fixed price preferred. Please share relevant examples of similar work when you apply.
Apart from that I’m also a full-stack developer with the right Gen AI experience, which makes me a solid plus for your team[but right now only vibecoding]
Check my recent gen ai projects… I built a native Android automation agent too. It’s worth a look:
I can build complex AI automations directly in code, not just inside n8n
I recently started posting my n8n work on YouTube with explanations:
I also completed a project where I used a PostgreSQL-based vector database, pulled user data, and automated promotional emails during trial periods (can’t share the workflow due to client confidentiality).
Fixed price is $400. I’m available for a call to review schema and email format before starting.
This is a clean and well-scoped build. I’ve worked on similar n8n workflows where data is queried from PostgreSQL, grouped/processed in Code nodes, and then sent out as structured emails on a schedule.
From your description, the key parts here would be:
• writing efficient PostgreSQL queries to fetch and group the records correctly
• handling the pairing / grouping logic inside n8n (Code node)
• formatting the email output cleanly before sending via Azure Communication Services
• ensuring the workflows run reliably on weekly and month-end schedules
A couple quick clarifications:
• for the pairing logic, is it based on a shared field (e.g. session_id or relationship key)?
• do you already have a preferred email template format, or should that be structured as part of the build?
I am Muhammad Bin Zohaib, an AI & Web Solutions Specialist, Full‑Stack Developer, and Certified n8n Developer (Level 1 & 2). I specialize in building production‑grade automations with error handling, idempotency, and complex multi‑branch logic.
Relevant experience:
PostgreSQL integrations inside n8n with custom queries and grouping logic.
Automated email workflows using Gmail API, HubSpot, and third‑party services.
Complex workflow orchestration with error handling and logging.
AI‑driven automation projects for clients across Canada, Greece, Singapore, India, Sudan, Spain, Australia, Germany, and the UK.
I am comfortable working on a fixed‑price basis and can deliver within the estimated 5–9 hour scope. Let’s align on requirements and I can provide a precise cost estimate.
This looks like a good fit for a bounded n8n and PostgreSQL email workflow build.
TinyOps can scope this as a fixed one-workflow build: confirm the query shape, build the weekly grouping logic, format/send through Azure Communication Services, add a dry-run test path, and document the handoff. I would keep month-end summaries as a second milestone unless the weekly workflow proves very small.
For a 5 to 9 hour project, TinyOps can start with a paid audit or a fixed build once the scope is confirmed. TinyOps Studio can be reached at support at tinyopsstudio dot com.
This is a very clear task, and I can get it done quickly since you already have the data ingestion and Azure connection ready. I specialize in building production-grade systems on self-hosted n8n instances (Docker/Ubuntu), so I’m very comfortable with your setup.
My Approach:
SQL & JS: I’ll handle the PostgreSQL queries and write the custom JavaScript in the Code node to manage the grouping and pairing logic.
Azure Email: I’ve worked with third-party mail APIs and will ensure the formatting for both parties (and the CC) is clean and professional.
Reliability: I’ll build this with error-handling to make sure the weekly and month-end summaries run without a hitch.
The Deal:
Fixed Price:$400 for the full setup (including testing and the month-end version).
Timeline: I can wrap this up in 1–2 days.
Availability: I have 25-35 hours free per week and can start immediately.
Relevant Work:
I recently built a similar automated notification system involving complex database logic and scheduled reports. You can see more of my work here: https://mikedevai.netlify.app/.
Given the workflows involve a few moving parts (data structure, pairing logic, email formatting, and edge cases like month-end handling), I usually break delivery into a few short milestones so we can validate each step before moving forward.
That way:
You can confirm the logic matches your data early
We avoid rework later
And you only pay for what’s been delivered and verified
Happy to start with a quick schema + logic validation step, then move into the workflow build.
Hi ignatius — clean scope. A few specifics from your post that match work I have shipped:
n8n Code node (JavaScript) for grouping logic — the “pair grouping” + “recipient grouping” pattern is well-trodden; standard approach is reduce() over query results to build the groups, then a Loop Over Items node firing one email per group.
PostgreSQL via n8n’s Postgres node — parameterised queries with $1, $2 placeholders, played safely against the connection pool.
Azure Communication Services email — n8n HTTP node POST to /emails:send (api-version=2023-03-31) with a JSON body: senderAddress, recipients.to/cc, content.subject + content.html. AAD or connection-string auth in the header. Polling /emails/operations/{id} for delivery status if you want confirmation receipts.
Month-end summary = clone the weekly workflow + adjust the SQL date range + tweak the email template. ~30% extra effort over the weekly.
Most relevant case study: a Custom Workflow Automation Engine I built for a non-tech client — query DB → group records → branded HTML email + PDF via Gmail API + scheduled follow-ups. Same shape as yours.
A few scoping qs to lock fixed price:
Roughly how many session records per week — drives one batched SQL vs paginate?
Email formatting: HTML with inline tables, or plain text?
Email priyanshukumarmaurya2224@gmail.com with answers and I will send fixed quote + 1-week timeline. Most builds in this shape land at the 5-7 hour mark once scope is locked.
Hi. I build n8n workflows on the JS-heavy side, with PostgreSQL queries in Code nodes and outbound mail via providers like Azure Communication Services and SendGrid. The two weekly workflows you describe
(group records into pairs, format statements, send with CC) plus the month-end summary fit into one n8n project with a shared template node.
Estimated time on my side: 5-7 hours. Fixed price $180 total, 50% on start, 50% after you confirm test runs against your DB. Payment via PayPal or USDT.
If you have a sample row schema and the Azure ACS sender domain ready, I can ship the first workflow within 36 hours. Happy to share a previous email-statement workflow on a quick call.
Clean brief, well-scoped, honest hour estimate. This is a straightforward build — PostgreSQL queries, grouping logic in a Code node, Azure email formatting. Right in your wheelhouse.
Hi,
This is a clean scope and I can deliver it within your 5-9 hour estimate. I work with PostgreSQL queries inside n8n regularly and have sent formatted transactional emails via third-party mail services including Azure Communication Services.
The grouping and pairing logic for both workflows I’d handle in a Code node — JavaScript for the record grouping, pair assignment, and recipient mapping before passing structured data into the email formatting step. Month-end variants would run the same query logic with a date range filter swapped in, so maintenance stays simple.
Relevant example: built a weekly reporting workflow for a B2B travel agency that queried Google Sheets, grouped records by client account across 50 active accounts, and sent formatted status emails to multiple recipients with copy logic. Same pattern as what you’re describing, different data layer.
Fixed price for both workflows can be discussed on a call Includes error handling, tested against your existing PostgreSQL schema, and a short handoff doc so your team can adjust query logic independently if needed.
Happy to jump on a quick call to review the database schema before starting.
This is a clean spec and exactly the kind of work I do well.
I have built production n8n workflows against PostgreSQL using the Postgres node and custom SQL in Code nodes, grouping records, joining across tables, and building formatted output for downstream nodes. Azure Communication Services is straightforward from n8n via the HTTP Request node with the right auth headers. JavaScript Code nodes for data shaping are standard in my workflow architecture.
The pattern you are describing, query, group, format, and send to multiple recipient sets with different CC logic, is a conditional routing problem inside n8n. I have built this exact pattern for multi-party notification workflows before.
I can take this from spec to tested, deployed workflows on your self-hosted instance. Happy to start with one of the two weekly workflows as a paid trial if that helps you evaluate fit before committing to the full project.
Hello @ignatius , welcome to n8n community, I have worked and have experience with n8n and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications
This looks like a good fit. I’m comfortable with PostgreSQL queries inside n8n, JavaScript in Code nodes, and sending formatted emails via third-party services — which is exactly what this project needs.
My relevant work:
E-commerce order notification system: webhook → data processing → formatted HTML email + Google Sheets logging
I’d like to understand the schema and email format requirements before giving a fixed price estimate. Happy to jump on a quick call or discuss via message.
I’ve built exactly this kind of workflow. I connected n8n to PostgreSQL with custom grouping logic in Code nodes, handled scheduled runs with error handling, and sent formatted emails via third-party APIs.
Relevant example: a CRM integration where n8n queries PostgreSQL, groups records by client, formats statements, and sends via API - currently running in production.
Building custom group logics and adding SQL while handling emails from 3rd party sources, seems like the project I delivered yesterday. I`m most efficient in making custom nodes that can bypass the code logic so you yourself can understand how automation is running in the end.
We can walk you through an exploration call and can give the exact blue print we`ll follow.
This looks like a clean, scoped automation build: scheduled PostgreSQL queries, grouping logic, formatted email output, and reliable delivery through the existing Azure Communication Services setup.
How I would approach it:
review the current PostgreSQL schema and existing ingestion workflow
define the grouping rules for each weekly statement
build the n8n Code node logic with clear inputs/outputs
add idempotency so the same statement is not sent twice by accident
create test runs with sample records before enabling the production schedule
document the workflow so your team can maintain or adjust it later
My background is in AI/API automation, JavaScript/Python scripting, CRM-style workflow logic, and business process automation. I am based in Spain and can work remotely and asynchronously.
Hello
This is exactly the kind of workflow where structure + reliability matters more than complexity — especially with grouped PostgreSQL data and multi-recipient email logic.
I’ve built similar n8n systems that handle database queries, data grouping, and conditional email routing using Code nodes + PostgreSQL, ensuring clean weekly/month-end automation without duplication or missed records.
For your case, I would structure the workflows to:
Efficiently query and group PostgreSQL records (weekly + monthly logic)
The main things I would check before building are idempotency, duplicate prevention, what happens when a pair/group is incomplete, and how Azure Communication Services failures get logged for retry instead of silently losing a statement.
I run WorkflowPatch async-only, so I am not the right fit if you need calls as the main path. If async is workable, send the relevant table shape, two redacted example rows, and the expected email format, and I can tell you whether it fits a fixed paid priority sprint.
I can also show a small public proof shape for the artifact format before you send anything sensitive.
