(HIRING)Automation Engineer Wanted — n8n Core Role — Restaurant Tech Startup

Jobs
1

RestaurantFlow OS is a revenue automation platform for independent restaurants. We intercept booking data from OpenTable and SevenRooms, run it through a workflow n8n automation layer, and personalise every guest interaction based on visit history.

The system architecture is complete. We have a full technical master spec covering every workflow, every data flow, every edge case and every error state. We are not asking someone to design this — we need someone to build it precisely, with clean error handling, idempotency on every inbound webhook, and a Loom walkthrough per workflow group.

The Stack You Connect

  • Supabase
  • GHL
  • Printnode
  • openweatherapp

The Architecture Principle

Every workflow validates restaurant_id as step one. Scheduled workflows loop through active restaurants one at a time — no state bleeding between clients. Idempotency checks on every inbound webhook using unique_event_id logged to Supabase event_log. HMAC-SHA256 signature validation on every inbound webhook. Error handler WF-20 catches all failures, logs full context, sends admin alert. This is not MVP code — it is production architecture from day one.

WHAT WE ARE OFFERING

:check_mark: Paid build fee for the initial workflow implementation — scoped and agreed upfront

:check_mark: Ongoing paid retainer — every new workflow, integration and optimisation as the platform scales

:check_mark: Equity stake for the right long-term partner

:check_mark: Your architecture credited in technical documentation and investor materials

A product that is genuinely novel — no existing platform does what RestaurantFlow does

Who We Are Looking For

→ Proven n8n experience with complex multi-branch logic, webhook handling, API integrations and error handler patterns.

→ Comfort building against a precise written spec — this is a defined architecture, not a creative brief.

→ Ability to deliver Loom walkthroughs explaining every workflow decision.

→ Ideally: experience with Supabase or PostgreSQL APIs, GHL API calls, or hospitality/restaurant technology.

Reply or DM — tell us the most complex n8n workflow you have built and what made it hard.

+4407440589544

heldermiranda96@gmail.com

The spec is ready. The clients are coming. The system needs to be built.

4 Likes
2

Hey :waving_hand:,

I’m Milan, with 8 years of experience in Business Automation and AI. Including 2 years at Apify working on enterprise-level browser automation.

Currently specializing in n8n, but also proficient in Python & Javascript.

Find out more about my work here:

If you think I might be a match, please:

Book a call here with me

Or reach out at hello@smoothwork.ai

Looking forward to hearing from you!

3

If you need I am available here:

I am one of top 50 verified template creators:

I am also capable of building custom community n8n node too:

  1. https://www.npmjs.com/package/n8n-nodes-pdfbro
  2. https://www.npmjs.com/package/n8n-nodes-ocrbro
  3. https://www.npmjs.com/package/n8n-nodes-ttsbro

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:

You can schedule a quick call with me: N8N Project Consultation with Vaar | Iamvaar | Cal.com

Fun fact… I even made an n8n workflow to find a few n8n project leads for myself so I truly believe in what I do…

9bSkKu
9bSkKu1220×1470 122 KB

I started asking My recent clients for honest feedbacks so here is one testimonial: https://www.youtube.com/watch?v=TqBy3SVCHgQ&list=PLAJltY5bp6yiZ3sFBjm7bfrkLXSGtJX8m

Here is my linktree: iamvaar | X | Linktree

And I am also capable of building gohighlevel automations and other CRM’s too, here are my recent gohighlevel integrated automation videos:

  1. https://youtu.be/eZ3t7PfXFho
  2. https://youtu.be/nSJzOB9JZlY

And I also built low latency voice appointment scheduler with live ai avatar[in code]:

I built AI search visibility tracker[I am capable of building complex web scraping automations in python too]:

And done many other big projects too which are under NDA’s so technically I can’t reveal them.

4

Hi Helder, Welcome to n8n Community :waving_hand:

This is a strong spec, especially the focus on idempotency + isolated multi-tenant flows.

I’ve built similar n8n systems handling webhook ingestion → validation → processing → logging with strict error handling and no state leakage across clients.

Recent builds: • AI voice + API workflow orchestration

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2038586338272239616

• Multi-channel automation (CRM + data + reporting flows)

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2039118619839795200

• Shopify backend workflow system

https://www.upwork.com/freelancers/~0122761e4734295f4b?p=2039336822638325760

Question: – how are you currently structuring event_log in Supabase for deduplication and replay safety?

Happy to take a workflow group and map it cleanly.

I’ll DM you as well.

5

This sounds like exactly the kind of build I do. Two things from your spec stood out: idempotency on every inbound webhook with unique_event_id logged to a Supabase event_log, and HMAC-SHA256 signature validation. That’s the architecture I default to — I’ve shipped it on a SaaS (CannaSpy) and on StoryStar’s AI generation pipeline, both with Supabase as the source of truth.

Fast questions before I send a structured proposal:

  1. Roughly how many workflows in the initial build scope?
    1. Is the spec doc shareable under NDA so I can size accurately?
      1. Self-hosted n8n or n8n Cloud?
    3. I can share Looms of past Supabase + n8n + Stripe builds. Happy to start with a paid 1-workflow trial so you can validate the build quality before committing to the full retainer.
6

Helder — the architecture you’ve laid out is the right shape. Where this breaks at scale: WF-20 becomes a single point of contention. When one restaurant throws an error during a scheduled batch, the queue stalls and every other restaurant’s workflow silently delays. The fix is per-tenant error handler isolation, not just idempotency on the ingest side.

I’ve shipped this pattern in production — a 9-agent multi-tenant system on Python + Claude API + Supabase + Slack — where the same isolation design caught $30K of ad waste in 30 days that the client’s existing tools missed. Public reference repo, Pydantic at every boundary, CI green:

I’ll send a 5-minute Loom showing exactly how I’d modify WF-20 to isolate per-restaurant failures, plus a sample n8n workflow with the tenant_id scoping pattern. Within 24 hours of your reply. Email: priyanshukumarmaurya2224@gmail.com

— Priyanshu
Portfolio: Work — Priyanshu Kumar

7

Hi Helder,

I’ve reviewed your project and want to apply

The most complex n8n workflow I’ve built:

I recently shipped an autonomous “AI Content & Lead Factory”. The hardest part was ensuring idempotency and state management across thousands of parallel executions. I used custom PostgreSQL logging for every event to handle retries without duplicating expensive API calls—essentially the same logic you’re requiring with unique_event_id in Supabase.

How I’ll handle the RestaurantFlow build:

  • Precision & Security: I’ll implement the HMAC-SHA256 validation and restaurant_id scoping as step one for every workflow to ensure zero data bleeding between clients.

  • Reliability: I’ll build the WF-20 error handler to log full context to Supabase and alert you immediately if anything slips.

  • Clean Code: Since I’m a developer (JS/Python), I’ll write custom logic for the Supabase, GHL, and Printnode integrations whenever standard nodes aren’t efficient enough.

  • Documentation: You’ll get a detailed Loom walkthrough for every workflow group, explaining every decision so the system isn’t a “black box”.

Why me?

I’m a professional AI developer and automation specialist based in Belarus. I’ve built complex CRM-to-PM syncs (Hubspot/ClickUp) and AI-driven business solutions where precision is mandatory. I’m looking for a long-term partnership and am ready to deliver code that is production-ready from day one.

My PROJECTS & Portfolio: https://mikedevai.netlify.app/

Contacts:

I’m ready to sign the NDA and dive into the spec today.

Best regards,

Mikhail

8

The most complex n8n workflow I have built is a 45-node autonomous CI/CD pipeline that takes a single service name as input and outputs a complete, production-ready npm package: TypeScript source, Jest tests, GitHub Actions workflows, and README, all generated in parallel via Claude AI API calls using Promise.all, published to npm, and tracked in Airtable. Build time is 4-11 minutes. What made it hard was managing parallel async execution within n8n cloud timeout limits, handling 10-20+ resources per node simultaneously without state bleeding between runs, and building reliable error routing that fails gracefully without corrupting the pipeline state.

Your architecture principle around idempotency and no state bleeding between restaurant maps is exactly how I had to solve the same problem across 162 live integrations.

I am comfortable with Supabase, GHL, n8n self-hosted, and webhook validation patterns. The spec-first approach you describe, full technical master spec before build, is how I prefer to work.

Portfolio: johndrefahl.com | Velocity-BPA (John Drefahl) · GitHub

Email: john@velobpa.com

9

Hey Helder,

Saw the post and wanted to reach out. I’ve been building with n8n for a while now and the stack you’re describing — Supabase, webhooks, multi-tenant architecture — is basically what I’ve been working with.

The most complex thing I built was a full WhatsApp ordering bot for a pizza restaurant. End-to-end, no human intervention. The flow goes through 6 states (IDLE → MENU → CART → CONFIRM → PAYMENT → ORDERED), all persisted in Supabase with optimistic locking to handle concurrent messages from the same user without race conditions.

What made it genuinely hard was the deduplication layer. Evolution API sometimes fires the same webhook twice, so I had to build idempotency checks on every inbound message using the message_id before touching any session state. Without that the cart would break on duplicate triggers.

I also built a cleanup workflow that runs every 30 minutes to handle abandoned sessions, plus a kitchen notification system that fires on order confirmation with the full order context.

The architecture was modular — one main workflow routing by state, separate sub-workflows per state. 8 workflows total. That made debugging much cleaner when something broke mid-conversation.

I’m comfortable building against a precise spec rather than designing from scratch. That’s actually how I prefer to work.

Happy to jump on a call or answer anything specific about how I’ve handled error states or webhook validation.

Santiago

10

Hi Helder. Your spec is the kind of n8n work I prefer: deterministic workflows, not fuzzy agent demos.

I would approach the first paid build as one workflow group, not the whole platform at once. I would implement restaurant_id validation as the first guard, HMAC verification before payload handling, unique_event_id insert/check in Supabase, and a tenant-scoped error path so one restaurant failure cannot block the rest of the scheduled loop.

For handoff, I would add a small test matrix: duplicate webhook, bad signature, missing restaurant_id, inactive restaurant, downstream API failure, and successful run. Then a Loom/runbook can document exactly how to replay or inspect failed events.

A practical first milestone could be one inbound webhook workflow plus WF-20 logging/admin alert integration against your spec. If that passes, the same pattern can be cloned to the other workflow groups.

If you are still hiring, I can review a redacted workflow group from the master spec and price the smallest paid implementation slice.

11

Hi maxim_makselyanov!

Saw your post about (HIRING)Automation Engineer Wanted — n8n Core Role — Restaurant Tech Startup.

I specialize in n8n workflow automation and have built end-to-end systems for:

  • CRM pipelines & lead generation automation
  • Multi-platform integrations (Google, Salesforce, HubSpot, custom APIs)
  • Custom AI agents with n8n (OpenAI, Anthropic)
  • Production error handling and monitoring

Happy to discuss your requirements. Feel free to DM or email!
BTW, I just released some free automation templates on Gumroad if useful: https://nxning.gumroad.com
Cheers!

12

Hi Helder,

This is the kind of n8n build I would take seriously because the spec already has the right production constraints: restaurant_id isolation, idempotency, event logging, HMAC validation, a central error workflow, and walkthroughs instead of a mystery build.

The hardest similar workflow pattern I would point to is multi-step intake/routing where a webhook event has to be normalized, checked against prior state, routed by tenant/customer context, logged, and either sent forward or held for review without double-sending. The hard part is not connecting nodes; it is making sure retries, duplicate events, partial failures, and missing tenant context do not bleed into the wrong account or create bad outbound actions.

For RestaurantFlow OS, I would suggest starting with one paid workflow group rather than the whole platform at once:

  1. inbound booking/guest event contract
  2. restaurant_id validation and event_log idempotency check
  3. Supabase write/read path
  4. one personalization branch
  5. WF-20 style error capture and admin alert
  6. Loom/runbook showing the happy path, duplicate event path, bad signature path, and failed downstream API path

That first slice would prove the architectural discipline before expanding across OpenTable, SevenRooms, GHL, Printnode, weather, and scheduled restaurant loops.

Proof links:

Commercial shape: fixed paid first workflow group, then retainer for additional workflows/integrations once the first slice passes your acceptance checks. I would quote the first controlled build slice at USD 1,200 after reviewing the spec and exact API boundaries.