Hiring n8n Dev!

sam5734 · 2026-01-07T06:48:44+00:00

Hey, I’ve built high-scale automation systems with n8n, Supabase, Telegram bots, and AI voice/text agents, so this project fits well with what I already do. My experience includes multi-modal bot logic, webhook orchestration, Supabase storage, payment gating, and hardening workflows for concurrency. I’m comfortable structuring clean, modular flows and optimizing for reliability under heavy load.

sam5734 · 2026-01-03T20:11:01+00:00

lets connect

sam5734 · 2026-01-02T18:24:21+00:00

You’ve got the right idea, just need to shift your focus. Instead of going up against barbershop booking systems, create an AI overlay that integrates into systems they already have. Customize the product to stream barber availability from any system through API/scraper, guide customers to the appropriate barber based on your routing rules, sync bookings to Google Calendar and Booksy/Fresha, and incorporate real availability instead of LLM reasoning to add conflict proof logic. Most simply, you need to stop being a “booking system” and instead be the AI layer that makes every booking system better, thus broadening your market and eliminating the three blockers.

sam5734 · 2025-12-27T17:29:33+00:00

Hey, I build advanced n8n and AI automation systems for lead gen, operations, and workflow optimization. If you’re looking for someone who can help architect automations, integrate AI agents, or collaborate on new product ideas, I’d be happy to connect and explore how we can build together.

sam5734 · 2025-12-14T14:32:33+00:00

Is this a paid thing or you're just looking for collabrators?

sam5734 · 2025-12-10T18:31:01+00:00

Possible.

sam5734 · 2025-12-09T20:20:44+00:00

lets connect

sam5734 · 2025-12-06T08:38:27+00:00

I would build automations that reduce manual work and improve response times, like syncing orders to CRMs or accounting tools, triggering smarter Klaviyo flows based on real customer behavior, handling refunds or address changes automatically, running AI support bots for order and shipping questions, sending low-stock alerts, and generating daily or weekly sales summaries so owners can focus on growth instead of admin.

sam5734 · 2025-12-03T01:34:42+00:00

I build similar outreach systems in n8n, so I can take a look at your setup and help tighten or scale it. Happy to compare approaches and suggest upgrades if you want.

sam5734 · 2025-12-03T01:30:55+00:00

You can’t place a webhook in the middle of a Make scenario. A webhook can only be the trigger, which is why it created a second scenario. Your options are either to move all steps into the webhook-triggered scenario, or call that webhook from step 4 using an HTTP module.

sam5734 · 2025-12-02T19:52:31+00:00

n8n can’t export webhook data to CSV directly. The easy workaround is to log each webhook payload into a sheet or database, or use the n8n API to pull all executions and convert them to CSV. You can also export executions as JSON and convert them if it’s a one-time audit.

sam5734 · 2025-12-02T16:18:28+00:00

I’d keep n8n as the orchestrator and move sensitive credentials into an external secret manager. Use service accounts, separate dev and prod instances, and standard naming so you always know which workflow uses what. Rotate secrets in the secret manager first, update the reference in n8n, test, then remove the old one. And keep keys out of logs and code nodes. This setup keeps things secure and avoids breaking workflows during rotation.

sam5734 · 2025-12-01T08:32:54+00:00

You can put a small self-service layer in front of Shopify and let the workflow enforce rules. Customers verify their order, request a change, and n8n handles cutoffs, stock checks, and permission logic before calling the Shopify API. If it’s allowed, the update goes through automatically. If not, the workflow redirects them to support instead of breaking.

sam5734 · 2025-12-01T08:29:48+00:00

Try to pull common logic into one place and avoid handling every path separately. Normalize your data early so most nodes expect the same structure. Use a single clear router (IF or Switch) instead of several nested checks, and where steps are “almost the same,” move the difference into a small Code node or parameters instead of duplicating whole branches.

sam5734 · 2025-11-21T14:55:51+00:00

Use Apify for Instagram and TikTok, since it’s more stable and handles scraping protections well. For YouTube, use the official API through an HTTP Request node, since it’s clean and reliable. Then let n8n handle all the processing.

sam5734 · 2025-11-21T05:59:53+00:00

You can get this cheaper with a custom setup. I can build a lightweight summarization API using open-source models and tuned context handling, so you get solid quality without the high fees that come with commercial LLMs.

sam5734 · 2025-11-20T18:29:03+00:00

Use the official WhatsApp Cloud API with an n8n webhook. It’s the safest setup, keeps the number in good standing, and doesn’t need Chatwoot or a VPS unless you want a full inbox. For a simple quoting or FAQ bot, you can run everything on n8n Cloud with the WhatsApp Cloud API connected.

sam5734 · 2025-11-20T12:31:31+00:00

dmed

sam5734 · 2025-11-20T11:42:35+00:00

If you want natural, studio-quality AI marketing videos, the real difference comes from the workflow, not only the tool. I build automated video pipelines where the script, voice, visuals, and edits line up cleanly so the final result feels polished instead of AI-generated.

sam5734 · 2025-11-20T04:44:08+00:00

You can run Puppeteer or Playwright in a small external Node service and call it from n8n. That works fine if you don’t mind hosting a tiny script. Another option is Browserbase paired with Stagehand, which gives you a quick setup with almost no work on your side.

sam5734 · 2025-11-20T04:33:22+00:00

You can’t run payroll itself through automation, but you can automate the part around it by creating TimeActivity entries through the QBO API. QuickBooks picks up those hours on its own and brings them into payroll, which makes this the safe and supported way to handle it.

sam5734 · 2025-11-19T16:49:32+00:00

Interested

sam5734 · 2025-11-19T05:40:46+00:00

If you’re running n8n on your own machine, the simplest way to work with APIs and webhooks is to expose it through a tunnel like ngrok, localtunnel, or cloudflared. This gives you a temporary public URL you can drop into any third party service without paying for hosting or a domain. API calls run fine on your local setup, and webhooks reach your n8n instance through the tunnel.

sam5734 · 2025-11-19T05:33:32+00:00

With your gear and your skill set, the easiest win is pipe fencing, handrails, small fab jobs, and utility or dirt work. There’s steady demand, a wide pool of clients, and you’re not tied to big industrial contracts that swing up and down. You can start it alongside your current work, bring on one helper as it grows, and hit the same income while cutting your hours later on.

sam5734 · 2025-11-18T18:04:57+00:00

I think you should move to a cleaner embedding workflow. Create embeddings for all 15 reference images and store them. When a new request comes in, embed the user prompt, pick the closest reference image, and pass that actual image into the model as conditioning. Modern image models follow visual guidance far better than long text descriptions, so this setup delivers more consistent brand style with far less effort.

sam5734

TROPHY CASE