email - alliance940404@gmail.com
Telegram - @seasonedtechguy
neckebiznis@gmail.com is my email
instagram @nemanjaaradovanovicc
Hi Nikolaos!
I build production n8n workflows daily — it’s my primary automation tool. My biggest project: 50+ n8n workflows for a WhatsApp recruitment platform (3,000+ candidates processed, Claude API scoring, auto-CV generation). Also running 12+ production AI systems on Railway.
Stack: n8n, Python, Claude/OpenAI APIs, PostgreSQL, Telegram/WhatsApp APIs.
Email: roberto.nasyrov@gmail.com
Telegram: @nasyrov_robert
Portfolio: robert-website-xi.vercel.app
Impressive scale with 10+ accounts. While others focus on just connecting video APIs, I specialize in building resilient, enterprise-grade architectures in n8n that don’t break when API limits or file sizes get heavy.
How I would optimize your 10-account pipeline:
– Conflict-Free Scheduling:
Integrating the pipeline with a master calendar (Google/Airtable) to ensure all 10 accounts have a balanced content flow without overlaps.
– Advanced Error Handling: Building “retry-logic” for heavy video rendering tasks—if an AI generator fails, the system auto-recovers without manual intervention.
– Voice-to-Video Synergy: Since I work deeply with Voice AI (Vapi/Retell), I can ensure the audio-visual sync and emotional tone of the avatars are perfectly aligned with the script’s intent.
I’ve just polished my infrastructure for high-load automations at Axon. Let’s connect to see how we can make your “Video Factory” not just functional, but indestructible.
✉️Portfolio/Contact:
email : nick@aiflowaxon.com
Telegram : @WakanaMK
Whatsapp : 89029319839
Hey Profile - Nikolaos_Zissidis - n8n Community
I got you, I have been building all forms of automations for the past 2 years and have built 100s of flows for my clients. Have worked with all sorts of companies and gotten them 10s of thousands in revenue or savings by strategic flows. When you decide to work with me, not only will I build this flow out, but also give you a free consultation like I have for all my clients that led to these revenue jumps.
I have built a similar workflow like this for one of my clients. I can not only share that but also how you can streamline processes in your company for faster operations. All this with no strings attached on our first call.
You can also email me at- Pmediaaryan@gmail.com
Here, have a look at my website and you can book a call with me there!
Talk soon!
Hi Nikolaos,
Your post stood out immediately — Shopify and n8n is where I’ve spent most of the last year.
I’ve built 70+ production n8n workflows for a live Shopify jewelry store: order management, inventory sync across platforms, customer notification sequences, and automated fulfillment logic. Not test projects — these run daily in production.
What I typically handle for e-commerce operations:
- Order to fulfillment to notification pipelines with zero manual touchpoints
- Inventory sync across multiple warehouses or marketplaces
- Shopify webhooks routing into CRM, email, or SMS triggers
- Returns and refund workflow automation
- Reporting to Google Sheets, Airtable, or custom dashboards
I deliver in 1-3 days per workflow, work async across time zones without hand-holding, and hand over clean documented n8n JSON exports you own completely.
Before I pitch anything specific — what’s the core problem you’re solving? Order volume, manual data entry, sync between platforms? Knowing the bottleneck lets me show you a relevant example from my stack.
Hey Nikolaos,
The pipeline architecture you described is something I build regularly in n8n - just with different data types. My production workflows follow the same pattern: input → AI processing (Claude API) → transformation → delivery.
Specifically, I have 4 production systems running right now that use Claude API through HTTP Request nodes with proper error handling and retry logic. One of them processes incoming data through 3 sequential AI calls, scores it, and routes output by priority - same architectural pattern your video pipeline would need.
For the video gen part - I haven’t worked with Veo specifically, but I’ve integrated plenty of external APIs through n8n. The pattern is always the same: authenticate, send request, poll for result, handle timeouts, process output. I also have a backend dev background (Python, JavaScript) so custom Code nodes are second nature.
I can figure things out independently - that’s how all my production systems were built.
Portfolio: github.com/penkayone/n8n-automation-portfolio
Email: An.goloskokov@gmail.com
Telegram - @antongoloskokov
Happy to DM or jump on a quick call to discuss the architecture.
Hi Nikolaos, I build exactly this kind of pipeline. At Elegance Academy I deployed a production n8n workflow integrating Claude API and OpenAI API for AI content generation and scheduling at scale — including JavaScript Code nodes, Google Drive integration, and multi-step enrichment. I’m comfortable working independently and can start immediately. Happy to share specifics — JT Goodnews | goodnewscode@gmail.com
im here
u can reach me on whatif0444@gmail.com
This looks like a good fit for a bounded n8n content-pipeline audit before committing to a larger long-term build.
TinyOps can scope this as a bounded n8n content-pipeline audit: map the competitor script intake, Claude prompt step, video-tool handoff, Google Drive storage, transcript slicing, and review/export points. I would keep posting/publishing outside the first workflow until outputs are approved.
A practical first pass would be a paid audit, then a fixed prototype for one content path if the scope is clean. TinyOps Studio can be reached at support at tinyopsstudio dot com.
Hi! I saw your post looking for an n8n specialist for Shopify e-commerce. I am a Systems Engineer and I have actually built a decoupled webhook architecture specifically to bypass the 3-second Shopify/Zendesk timeout limits for high-latency AI tasks.
I build production-grade, fault-tolerant workflows that don’t break. You can see my actual n8n architectures here: Notion Portfolio. Let me know if you are free for a quick chat today.
This is a good fit. I build production n8n workflows with Claude API for script generation, Google Drive integration, and multi-step AI pipelines. The pattern you are describing, competitor input, AI script generation, video output, transcription, and ready-to-post formatting, is a multi-phase n8n pipeline with Claude handling the content layer.
I have not built with Veo specifically but I work with AI APIs daily and pick up new tools quickly. If they have an API or webhook, I can integrate it.
I work independently and deliver working systems, not prototypes. 162 published n8n community nodes under @velocity-bpa if you want to see the depth of my n8n work.
Portfolio: johndrefahl.com | Velocity-BPA (John Drefahl) · GitHub
Email: john@velobpa.com
Hi Nikolaos,
I am interested in this project.
The pipeline you described is a good fit for the type of automation systems I build: multi-step AI workflows, API integrations, structured data between steps, JavaScript logic where n8n nodes are not enough, and clear error handling so the workflow can keep running reliably.
For this video generation system, I would structure it in stages:
- intake and storage of competitor scripts/prompts in Google Drive or a database
- AI script rewriting/variation with Claude
- generation queue for video/avatar tools
- transcription and segmentation into short clips
- validation/status tracking so failed items can be retried instead of lost
- final output organized for publishing across the social accounts
I am based in Spain, available for remote async work, and can start with a small paid pilot to prove the approach before scaling the full pipeline.
Reach me here or at: jorgelg1177@gmail.com
Hey Nikolas
This project will contain an AI Agents thatll make the script for your videoes and once the script is finalized, itll build most suitable characters for your vidoes. In marketing, your words define you more than your product. Ive build many custom logic AI agents thatll do the work for you. You can have a look on my portfolio and then we can proceed!
Hi Nikolaos,
I would split this into orchestration first, media generation second.
First proof slice:
competitor prompt/script input → Claude script draft → scene/status ledger → AI video request step → Google Drive folder/status row + human approval/error path
That proves the handoffs, naming, approvals, retries, and asset tracking before the workflow is tied to every video tool and social account.
My lane is written and fixed-scope. If that fits your working style, send one competitor-script example, the target Drive folder structure, and the fields you want tracked for each output clip. I can tell you whether a fixed first sprint is realistic.
I can also show a small public proof shape for the artifact format before you send anything sensitive.
Alex Reed
WorkflowPatch
Hi,
I can help with e-commerce automation workflows.
For Shopify/e-commerce, I can work on:
- order/customer data sync
- Google Sheets / Airtable / CRM updates
- email or Slack/Telegram alerts
- AI classification of support requests
- product/feed processing
- reporting workflows
- API integrations and error handling
I prefer building simple reliable workflows first, then improving them with logs, retries and documentation so they are easy to maintain.
If you can share the main workflows you need automated, I can suggest a clean implementation plan.
Hi Nikolaos — this is close to the kind of bounded workflow I can help with.
For your Shopify/content pipeline, I’d build it in small testable stages first:
- competitor script/prompt intake → structured brief
- Claude script variations + brand constraints
- AI video generation step with status/error logging
- transcript split into ~8s segments
- Drive folder output + Sheet tracker for “ready / failed / needs review”
I’d avoid promising the whole long-term system before a small proof-of-concept. A good first milestone would be one working end-to-end sample from prompt → Drive output, with logs and handoff notes.
Contact: travisofwork@gmail.com
Happy to start with a fixed-scope test task if you’re still looking.
Hi Nikolaos — this is close to the kind of bounded workflow I can help with.
For your Shopify/content pipeline, I’d build it in small testable stages first:
- competitor script/prompt intake → structured brief
- Claude script variations + brand constraints
- AI video generation step with status/error logging
- transcript split into ~8s segments
- Drive folder output + Sheet tracker for “ready / failed / needs review”
I’d avoid promising the whole long-term system before a small proof-of-concept. A good first milestone would be one working end-to-end sample from prompt → Drive output, with logs and handoff notes.
Contact: travisofwork@gmail.com
Happy to start with a fixed-scope test task if you’re still looking.
Hey @Nikolaos_Zissidis — this pipeline is a good fit for me.
I build n8n workflows in production and have experience chaining AI APIs end to end. The structure you’re describing — competitor script input → Claude for script generation → AI video API call → transcription segmentation → organized output to Google Drive → ready-to-post — is a multi-step async workflow problem that n8n handles well if you build it correctly.
A few things I’d think through up front: video generation APIs like Veo are async by nature, so the workflow needs a polling or webhook loop rather than a linear step, otherwise it times out waiting. The 8-second transcription segmentation is straightforward with a Whisper API call plus a JavaScript Code node to slice the transcript. Avatar overlays would depend on which tool you’re using for that layer.
With 10+ social media accounts feeding the pipeline, the architecture matters — each account probably needs slightly different script parameters or output metadata, so I’d build account context in from the start rather than retrofitting it later.
Background on me: self-taught, built automations for real clients in manufacturing and e-commerce contexts, comfortable with Claude API, custom JS Code nodes, and Google Drive integrations. Available for long-term work right now.
Quick question: are the competitor scripts coming in as text prompts manually submitted, or is there a scraping/intake layer upstream that needs to be part of the build too?