Hi Ruben — your stack and “product owner of automation systems” note makes sense. The biggest win is probably not just building flows, but keeping a clean backlog: quick fixes, measurable automations, and weekly reliability checks.
A practical first paid task could be one contained workflow: lead/source intake → enrichment/AI summary → Notion or dashboard status → Slack/WhatsApp alert, with error handling and handoff notes. That gives you a useful delivery plus a way to judge fit before a larger ongoing role.
I work with n8n/Make, APIs, Sheets/Notion, OpenAI/Claude, and workflow QA. Happy to scope a small first automation.
Contact: travisofwork@gmail.com
Hi RubenNeedles - this covers exactly my stack.
The product-owner element is what makes this interesting. I manage n8n deployments end-to-end, not just build them and hand off. That includes triaging bugs, scoping feature requests, and being the technical owner in weekly alignment calls.
On the specifics:
Meta Ads automation: I have built workflows hitting the Meta Graph API for campaign operations, including creative variation pipelines with AI-generated copy.
LinkedIn/Indeed scraping and sales outreach: I build Lemlist-connected outreach sequences with AI enrichment in the middle to personalize at scale.
WhatsApp API: I have integrated WhatsApp Business API for automated notification and follow-up flows in n8n.
Stack alignment: n8n is my primary tool, Make is familiar. I can work across both and advise when to route which workflows where.
Fluent English, fully remote, available now.
Contact: narotsuhail@gmail.com
Hey Ruben — this is exactly the kind of role I’m looking for.
I build and maintain production automation systems end-to-end. The stack you listed (n8n, Make, OpenAI/Claude, Meta Graph API, WhatsApp API, Notion, Lemlist) is what I use day-to-day. A few things directly relevant to what you’re building:
**Meta Ads automation**: I’ve connected to the Meta Graph API for Facebook Pages + Instagram — ad creative distribution and status reporting are things I’ve handled as part of a daily content pipeline.
**LinkedIn/Indeed scraping for outreach**: Built LinkedIn search-based lead sourcing pipelines (n8n + Apollo) that feed enriched contacts directly into outreach sequences.
**Sales & outbound flows**: Apollo + Lemlist-style sequences, webhook-triggered follow-up logic, lead scoring triggers.
**Dashboards**: n8n → Google Sheets / Notion pipelines with scheduled sync and Slack alerting for anomalies.
The product owner aspect appeals to me. I’m used to being the person who triages, prioritises, and pushes back on feature creep — not just the person who executes tickets.
I’m based in South Africa (UTC+2), fully remote, fluent in English, and available for the weekly alignment call. Rate is negotiable — happy to discuss.
DM me or drop your contact here and I’ll follow up.
-– Suhail Narot | Fajr AI | narotsuhail@gmail.com
Ruben, this fits my lane. I can help own n8n/Make automations around approved-source data, dashboards, Meta/WhatsApp/API flows, reporting, bug triage and handoff docs.
My background is 17+ years in enterprise systems, API/data validation, SQL/ETL, production support, UiPath, Power Automate, Make/Zapier and n8n. A relevant example: built/led lead enrichment and scoring workflows with validation, retries and business-team handoff.
If useful, send one workflow that is causing friction and I will scope a first paid milestone.
Hi Ruben,
This fits the kind of automation work I’m looking for: practical n8n/Make/API systems with testing, docs, and ongoing maintenance rather than one-off demos.
For a first paid task I’d keep the scope small so you can judge reliability:
- take one existing repetitive ops workflow
- map the trigger, data fields, and failure cases
- build the n8n/Make version with clear logs
- add a simple QA checklist and handoff notes
- leave it easy for your team to adjust later
Good first candidates from your list would be reporting automation, outbound lead enrichment into a Sheet/CRM, or a small Meta/creative ops workflow with human approval before anything is published.
I’m based in Tashkent, work async, and can start with a fixed-scope test task or workflow audit.
Best,
Tim
hi ruben,
this sounds very aligned with the kind of automation work i enjoy building.
my work primarily centers around n8n-based systems, ai workflows, api integrations, and extending automation platforms with custom backend or scripting logic where standard no-code patterns fall short. i tend to work best in environments where workflows are tied directly to business operations rather than isolated experiments.
what stood out to me in your post is the ownership aspect. i’m comfortable not only building workflows, but also maintaining and improving them over time, troubleshooting edge cases, evaluating feature requests, and keeping systems stable as operational needs evolve.
some areas i regularly work in:
-
ai workflow orchestration
-
lead and outbound automation
-
structured data extraction
-
api integrations
-
operational dashboards and reporting pipelines
-
custom n8n code nodes and integrations
-
python/javascript extensions for workflow systems
a few examples of my work:
n8n creator profile: https://n8n.io/creators/wizard/
published npm nodes: https://www.npmjs.com/~victor-folorunso
one recent project involved building an automated website ingestion and rag pipeline in n8n with custom processing logic, external apis, and maintainable workflow orchestration.
i’m also comfortable working asynchronously and collaborating directly with founders on prioritization and iterative improvements rather than only working from rigid specifications.
if you think i might be a fit, feel free to message me here or reach out directly at victorfolorunsoofficial@gmail.com.
would be interested to hear more about the systems you’re currently building and where the biggest automation bottlenecks are.