[Hiring] n8n Automation Specialist — Paid, Long-Term, Remote (E-Commerce / Shopify)

Jobs
43

Hi,

I’ve built exactly this kind of AI video content pipeline — and I run one in production right now.

Live system I currently maintain:

  • n8n workflow that picks a daily product, passes it to HeyGen to generate a short-form video with an AI avatar, then auto-posts to Meta (Facebook + Instagram) at a scheduled time
  • Stack: n8n + Claude API (script generation) + HeyGen API (video) + Meta Graph API (auto-post) + Google Drive (asset storage)

For your specific pipeline I’d build:

  1. Competitor script ingestion → Claude API to rewrite into your brand voice
  2. AI video generation via HeyGen or Veo (matching your avatar requirements)
  3. JS Code node to split output into 8-second clips with transcription alignment
  4. Google Drive output organised by account/date, ready for your social team
  5. Multi-account handling across your 10+ social accounts

I work independently — give me the vision, I build the thing. Paid, long-term remote is exactly my model.

DM me or email narotsuhail@gmail.com — happy to show you the live pipeline on a quick call.

— Suhail Narot | Fajr AI | fajrai.net

44

This is exactly what I built for a retail brand last month — a daily AI video pipeline running in production. Here is the architecture I delivered, and how it maps to what you need.

What I built for the client:

A scheduled n8n workflow that fires every morning, selects a product from a Shopify store using Claude API to write the script, opens HeyGen via browser automation to generate the avatar video, and then posts the output to Meta (Facebook + Instagram) at 10AM. The whole thing runs unattended daily.

How this maps to your requirements:

Script intelligence: Claude API takes competitor content and product context and generates the video script. I have already built this prompt chain for a retail use case and can adapt it to your brand voice and competitor angle.

Video generation: I used HeyGen for avatar-based video. Veo / Google Labs can slot in at the generation layer — the n8n workflow just changes which API call it makes. I can build it to support multiple backends.

8-second increment transcription: Handled via a JavaScript Code node in n8n — split the transcript by duration markers, align to video timestamps, output ready chunks.

Google Drive output: Google Drive API is straightforward in n8n — finished videos land in the right folder structure automatically.

Multi-account support: With 10+ social media accounts, I would build per-account scheduling logic in n8n so each account gets its own queue, rate limiting, and error handling without cross-contamination.

Why this is different from most replies you will get:

I do not need to figure out the architecture. I ran this in production for a real client. The pipeline has error handling, retry logic, and a daily canary check. I can show you the workflow structure on a call.

I am based in South Africa, fully remote, immediately available. DM me or reach me at narotsuhail@gmail.com.

45

Hi Nikolaos,

I can help with a bounded first slice of this instead of trying to promise the whole content engine upfront.

For a paid test build I would map one end-to-end path:

  • competitor script/prompt input
  • Claude script variation with your brand constraints
  • AI video generation handoff/status tracking
  • Drive folder output
  • Sheet tracker for ready / failed / needs review
  • short runbook so your team can extend it

The key risk is reliability around AI video tools and long-running jobs, so I would add logs and human review points early.

Contact: travisofwork@gmail.com

Best,
Tim

46

Hi Nikolaos,

I can take a scoped first build for this. I am strongest on n8n/API orchestration, JavaScript Code nodes, Claude/OpenAI-style prompt flows, Google Drive organization and reliable handoff docs. I would start by locking the video/avatar tool boundary instead of overbuilding a full content factory before the APIs are clear.

A good first milestone would be: competitor script or prompt intake → Claude script/storyboard → Drive folder/status tracker → selected video tool API call → transcript/segment metadata → ready-to-review output, with logs, retry points and a manual approval gate before posting.

If that proof workflow works, it can expand across the 10+ accounts. I would quote it as a fixed paid milestone once the available video/avatar provider and one sample input are confirmed.

Carlos
carlos.silveira.amaro@gmail.com