Hiring: Sales Tech & Automation Specialist (Ongoing Remote Work, CRM + Databases)

Jobs
21

Hi,

I’d be a good fit for the technical side of this. I build and debug n8n automations day to day — CRM fields and pipelines, webhooks, API integrations between tools that were never designed to talk to each other, and the error handling that stops a broken automation from failing silently for three weeks.

I’ll be straight about one thing: I’m not a JavaScript developer. I work with the nodes, expressions and API integrations, and I reach for code only when there is genuinely no other way. Most of what you listed doesn’t need it.

Examples of what I deliver, from a simple form-to-CRM flow up to an AI agent grounded in a client’s own documents that cites its sources and refuses to invent an answer when the information isn’t there: Portfolio — 3 tiers of work, with a 1-min demo

Available immediately, remote, and I work in writing. Happy to start on one broken automation so you can see how I work before committing to anything ongoing.

— Nathan (Nexum)

22

Hi Nicolas, saw you’re running a sales agency and juggling Close CRM alongside n8n/Make/Zapier/Airtable/Calendly — that’s exactly the kind of stack we help agencies simplify and keep running reliably.

We’re FortuneEdge AI Solutions — we build and maintain n8n automation workflows (lead capture, CRM sync, nurture sequences, reporting) so you’re not the one debugging broken automations at 11pm.

Pricing is straightforward: Starter (€1,500 setup + €500/mo) for one workflow, Pro (€2,500 + €900/mo) for 2-3 workflows with CRM sync, or Enterprise (€4,000 + €1,500/mo) for a full multi-channel setup with reporting. Monthly maintenance is included/mandatory and covers version updates, API compatibility fixes, bug fixes, and ongoing support.

Happy to chat here or over message about what would actually move the needle for you.

23

Hi, this is squarely what I do. I’m an automation specialist working mostly in n8n and Make, and the “keep the sales stack running and fix it fast when it breaks” part is the work I actually enjoy rather than tolerate.

Your stack is familiar ground: n8n and Make for the flows, webhooks and REST APIs to tie tools together, Airtable and SQL as the backbone, and Calendly, Typeform and ClickFunnels feeding the top of it. Honest on one point, my main CRM hours are GoHighLevel and Monday.com rather than Close, but the pipeline, field and status logic maps directly and I pick up a new CRM fast. I write JavaScript in code steps when the standard nodes run out of room.

Closest proof: I built a B2B outbound engine in n8n (sourcing, email verification, site scraping, personalization, then into the sending tool) that booked a client 17 qualified meetings in its first month, plus the unglamorous side, retries, error branches and alerting so a broken run pages me instead of silently dropping leads.

I’m after ongoing work too, not a one-off, and the “grow into broader technical ownership” part is exactly the direction I want. Fully remote, comfortable on US and EU hours. Happy to start small on one messy or broken automation so you can see how I work before anything longer term. What’s the best way to send you a bit more?

Best,

Nishant

24

Hi Nicolas,

I build in n8n and API integrations – most recent: a live knowledge base where n8n handles all the retrieval logic, Claude processes and responds, and Notion holds 167+ structured records in production daily. Different domain than sales, same architecture discipline: webhook in, map and validate, route conditionally, update the record, alert if something breaks.

Your stack (Close + Airtable) is new to me specifically, but that’s an API integration and schema mapping problem, not a foreign language. I prefer to understand a system completely before touching it, document what I change, and make sure the same failure doesn’t happen twice.

The ongoing, growing-into-technical-ownership structure is exactly what I am after.

Give me one broken or messy automation. I will show you the fix and the documentation.

Jason

25

Hi Nicolas,

I will keep this practical because you have already received plenty of general automation pitches.

I am an AI and automation consultant based in Spain, working with n8n, APIs, webhooks, OpenAI, Google Workspace, databases and business-process automation.

My strongest contribution would be taking ownership of the unreliable parts of an existing sales stack:

  • tracing where leads or field updates are lost;

  • identifying silent failures and duplicate executions;

  • correcting webhook, API and data-mapping issues;

  • adding useful retries, logging and alerts;

  • documenting the change so the same issue does not need to be investigated twice.

I have not used Close CRM as my primary CRM, so I would not pretend otherwise. However, the work you describe is fundamentally API, schema, state and workflow logic, which is exactly the type of problem I handle.

Rather than proposing a large engagement, I suggest starting with one paid diagnostic task:

  1. you select one workflow that is unreliable or requires repeated manual intervention;

  2. I map the failure path and identify the root cause;

  3. I implement or propose the smallest safe correction;

  4. I return the workflow with concise documentation and monitoring recommendations.

I can offer that initial diagnostic for €150 fixed, assuming it is limited to one workflow and access is properly scoped. If the collaboration works well, I am interested in ongoing maintenance and broader technical ownership.

I am based in the EU and can work comfortably across European hours, with some overlap into US hours.

Juan Molina
IA Consulting
https://iaconsulting.ai

26

The part of your post that stood out: you don’t want a one-off build, you want someone who keeps the stack *healthy* — debugging broken workflows, owning the CRM structure, and tightening the data flow between disconnected tools over time. That’s the work I actually prefer.

Quick map to your stack: Close pipelines/fields/views, n8n + Make + Zapier orchestration, Airtable + SQL as the data layer, and the webhook/API glue (incl. JS code steps) between Calendly, Typeform and ClickFunnels. My default approach to a messy inherited setup is to first instrument it — log failures so recurring breakages become visible patterns instead of surprise fires — then fix root causes, not symptoms.

I’m in the Israel timezone, which gives you the European-hours overlap you mentioned for US-client support.

Could we do a 20-min call so you can walk me through where it’s breaking most right now? I’ll tell you straight what I’d stabilise first.

— Michael, Linkrra

27

This lines up with the kind of work I like most: contained sales ops systems fixes where the result can be tested and handed back cleanly.

The lane I would be useful for first is not broad ownership. It is a small trial slice such as:

  1. one broken or unreliable CRM handoff
  2. one form, calendar, or funnel trigger
  3. one destination table, CRM object, or pipeline update
  4. one notification or exception path
  5. test records covering success, duplicate, missing-field, and failure cases
  6. short handoff notes so the team knows what changed

That gives both sides a practical way to judge fit before talking about ongoing ownership.

If that is useful, I can help scope one sales workflow issue into a small paid test task.

28

Sales-ops automation on a retainer basis makes a lot of sense — it’s the kind of work where the initial build is maybe 30% of the effort and the ongoing tuning is what actually keeps it useful. If you’re scoping this in n8n, a few things that tend to eat time: CRM field mapping drift (especially Salesforce/HubSpot custom fields changing), lead routing logic that needs to handle edge cases your client keeps “discovering,” and keeping webhooks healthy when the source system silently changes API versions. I’d build in a monthly audit checkpoint as part of the retainer rather than just reactive fixes. Full disclosure: my company builds done-for-you AI agents and automation for teams without in-house AI folks. What CRM stack are you working with here?

29

Sales-ops automation on a retainer basis makes a lot of sense, it’s the kind of work where the initial build is maybe 30% of the effort and the ongoing tuning is what actually keeps it useful. If you’re scoping this in n8n, a few things that tend to eat time: CRM field mapping drift (especially Salesforce/HubSpot custom fields changing), lead routing logic that needs to handle edge cases your client keeps “discovering,” and keeping webhooks healthy when the source system silently changes API versions. I’d build in a monthly audit checkpoint as part of the retainer rather than just reactive fixes. Full disclosure: my company builds done-for-you AI agents and automation for teams without in-house AI folks. What CRM stack are you working with here?

30

Hi @Nico_RevOps — debug/maintain/improve across n8n/Make/Zapier + Close/Airtable/SQL fits well, and JS/Python is no problem. You mention wanting someone calm when things break — my first week wouldn’t be building new things, it’d be adding dedicated error workflows + monitoring/alerting on the existing systems, so failures surface to you before they reach clients. Improvements on a stable base after that. I’ve got EU-hours overlap. Portfolio: Tobias Gensicke — Full-Stack-Entwicklung & KI-Automatisierung . Want me to take one small maintenance task first so you can see how I operate?

31

Hi Nicolas,

I’d like to apply for the Sales Tech & Automation Specialist role.

I build and maintain production n8n workflows — including an AI business assistant integrated with Google Sheets (6 separate tools, each locked to specific fields to keep data clean) and Gmail, plus scheduled workflows that aggregate data and auto-generate reports. I’m comfortable with webhooks, REST APIs, and debugging workflows step by step when something breaks — I can usually rebuild or fix an n8n workflow from scratch within minutes once I understand the logic.

To be upfront: my direct experience is strongest in Google Sheets rather than Airtable, and I haven’t worked with SQL databases yet. Both are things I’m actively picking up, and given how quickly I’ve adapted to new tools so far, I don’t expect either to be a long ramp-up.

I’m looking for ongoing work, not just one-off projects, so the structure of this role is exactly what I’m looking for.

GitHub: chitranshi0613 · GitHub
Live demo: nexora-rag-chatbot.streamlit.app

Happy to do a quick call or a short test task if useful. Looking forward to hearing from you.

Best,
Chitranshi

32

Hi Nicolas

“fails quietly, nobody notices” is exactly the failure mode I build against.

I run n8n workflows with retry + backoff on API calls, and when a call still fails after retries, it routes to a dead-letter path with a Slack alert instead of silently dropping the record — so a rep never wonders where a lead went, they get pinged instead.

I also run a self-hosted n8n + PostgreSQL stack with a tested backup → wipe → restore cycle, so a broken system is recoverable, not just patched.

Portfolio (real, importable JSON, not mockups): GitHub - tuhinn001/n8n-automation-portfolio: n8n automation portfolio with tested backup and restore. · GitHub

I already submitted the form, but happy to start narrow and prove fit first — pick one workflow that’s currently breaking or flaky, and I’ll audit it, fix it, and document what changed, as a small paid trial before anything ongoing.

What’s breaking most often right now, and is Close CRM your main system?

— Rashadul Hassan

33

Hi @Nico_RevOps, this role is a strong fit for me. I build and maintain n8n workflows, CRM automations, and database integrations daily at Delos Intelligence in Paris. My stack matches yours closely: n8n (cloud + self-hosted), Close CRM, Airtable, SQL databases, webhooks, API integrations, and JavaScript code nodes. I’m comfortable debugging broken automations step by step, maintaining CRM pipelines and smart views, and documenting recurring issues with clear fix recommendations. Based in Paris (CET), overlap with European hours is natural. I’m looking for ongoing work, not one-off projects. Email: julien_carr@delos-int.dls.so

34

Hi Nico,

This role fits well with what I do — I’ve built and currently maintain production n8n automation workflows (email outreach/follow-up sequences and social media automation), so debugging and improving live systems is exactly the kind of work I’m used to.

On your stack: I have hands-on experience with n8n, webhooks, and API integrations (Gmail/Google Workspace, Facebook, LinkedIn, plus multiple LLM APIs — OpenAI, Gemini, Groq). I haven’t worked with Close CRM or ClickFunnels specifically, but I’ve picked up new tools quickly in past projects — the underlying logic (pipelines, triggers, API connections) is the same across most CRM/automation platforms.

A few things about how I work: I built my current systems with production reliability in mind — rate limiting, error handling, and monitoring — not just “it works once.” I’m comfortable debugging messy workflows step by step, and I’m based in Slovakia (CET), so there’s solid overlap with both European and US working hours.

I’m specifically looking for ongoing, long-term work rather than one-off projects, so the structure here is exactly what I’m looking for.

Happy to share more detail on what I’ve built, or do a quick call/technical chat if useful.

Best,
Nuredin

35

We’re AbSun Studio, a technology and automation team focused on building and maintaining practical business automation systems. Our experience includes n8n workflow automation, API integrations, database-driven workflows, AI automation, lead generation systems, and JavaScript-based workflow logic.

We’re comfortable troubleshooting workflows step by step, connecting different tools through APIs and webhooks, working with structured data, and improving existing automation systems. We’re particularly interested in ongoing work where we can help maintain, debug, and continuously improve a growing automation stack.

You can learn more about our work here:https://absunstudio.com

36

Hi! I am an n8n workflow developer experienced in building custom automation bots, handling Webhooks, API integrations, and database connections (PostgreSQL/MySQL). I am available for project-based tasks or ongoing work. Feel free to send me a message with details so we can discuss how I can help you!

37

Здравствуйте, Invest_Tur.

Я внимательно ознакомился с вашим описанием через перевод. Сразу уточню: я нахожусь в Китае и предпочитаю письменное async-общение на английском. Если такой формат вам подходит, я был бы заинтересован начать с небольшого оплачиваемого MVP.

Отвечу по вашим 5 пунктам.

1. Какие похожие боты/автоматизации я делал?

У меня пока нет идентичного кейса Telegram-бота для недвижимости, поэтому я не буду выдавать другой проект за аналогичный.

Мой ближайший реальный проект — работающая B2B lead automation system на n8n.

Процесс включает:

  • импорт исходных лидов;

  • очистку и нормализацию данных;

  • проверку и дедупликацию по email/телефону;

  • lead scoring;

  • маршрутизацию лидов по статусам;

  • Google Sheets;

  • автоматическую email-отправку;

  • отслеживание ответов и ошибок доставки;

  • обновление статусов и follow-up;

  • отслеживание WhatsApp outreach;

  • webhook/API-интеграции.

Я сам собирал, тестировал, отлаживал и продолжаю поддерживать эту систему.

Поэтому мои сильные стороны — n8n, Google Sheets, пошаговая обработка данных, workflow logic, status tracking, webhooks/APIs, обработка ошибок и построение надёжных бизнес-автоматизаций.

2. Есть ли демо, скрины или ссылки?

Да. Здесь мои workflow examples и portfolio:

Это не Telegram real-estate bot, поэтому я не буду представлять его как идентичный кейс.

Portfolio показывает архитектуру и реальные automation workflows, которые я уже построил и поддерживаю.

3. Как бы я собрал такого Telegram-бота?

Для первого MVP я бы специально не усложнял архитектуру:

Telegram Bot → 7–10 вопросов → n8n → Google Sheets → OpenAI/Claude → Telegram notification

Логика первого этапа:

  1. Пользователь запускает Telegram-бота.

  2. Бот последовательно задаёт 7–10 вопросов.

  3. Пользователь идентифицируется по Telegram chat/user ID.

  4. Ответы сохраняются пошагово вместе с текущим статусом диалога.

  5. Source/referral сохраняется из Telegram start-параметра в отдельное поле.

  6. После последнего вопроса n8n собирает все ответы и отправляет их в OpenAI или Claude.

  7. AI возвращает короткий структурированный summary по потенциальному клиенту.

  8. Ответы, referral source и AI summary сохраняются в Google Sheets.

  9. Вы автоматически получаете Telegram-уведомление с данными нового лида и AI-выводом.

Также для MVP я добавил бы базовую обработку ошибок и защиту от повторной отправки данных.

Для первого этапа я предлагаю использовать Google Sheets, чтобы быстрее запустить и проверить сам funnel.

Если MVP покажет результат, на втором этапе можно добавить:

  • CRM;

  • payment integration;

  • Supabase;

  • более сложную qualification logic;

  • property matching;

  • дополнительные AI-функции.

Я бы не включал всё это в первый milestone, чтобы не раздувать MVP до проверки основной идеи.

4. Сколько будет стоить первый MVP?

Для описанного выше ограниченного первого этапа предлагаю:

USD 250 fixed

В scope входят:

  • Telegram Bot с 7–10 вопросами;

  • сохранение ответов;

  • source/referral tracking;

  • Google Sheets;

  • OpenAI или Claude summary;

  • Telegram notification;

  • базовая error handling;

  • защита от duplicate submission;

  • тестирование workflow;

  • передача готового n8n workflow.

В первый milestone не входят:

  • CRM integration;

  • payment integration;

  • advanced property matching;

  • сложный backend;

  • дополнительные боты.

Эти функции можно оценить отдельно после того, как основной MVP заработает.

5. В какие сроки смогу показать рабочую версию?

Ориентир — 7 дней после согласования scope и получения необходимых данных.

Перед стартом мне понадобятся:

  1. список 7–10 вопросов в нужном порядке;

  2. язык первой версии бота;

  3. пример желаемого AI-вывода;

  4. подтверждение, что для первого MVP используем Google Sheets;

  5. Telegram Bot token/test bot access и API credentials для выбранной AI-модели.

Критерий готовности первого MVP будет понятным и проверяемым:

Пользователь открывает бота по referral-ссылке → проходит 7–10 вопросов → ответы и источник сохраняются → AI создаёт summary → данные записываются в Google Sheets → вы получаете уведомление в Telegram.

Если такой scope вам подходит, я буду рад начать с небольшого оплачиваемого MVP и сначала показать качество работы на первом проекте.

Best regards,
Tao Li

38

Hi, this is the part of the job most applicants will skip over: debug and maintain. That is the work I actually like, and it is where I come from.

Fifteen years running industrial and commercial operations before I specialised in automation, so I read a broken pipeline the way I used to read a stalled production line: find where the state got lost, not where the error message appeared.

What I run in production today, with n8n and Airtable: an operations system for a construction company tying quotes, site interventions, invoicing and cash-flow tracking together, and a WhatsApp AI sales agent for a real-estate agency that qualifies leads, books and reschedules appointments, logs to a mini-CRM and hands over to a human the moment the conversation leaves its defined scope.

Two things from that experience that apply directly to a sales stack:

Calendar and CRM sync breaks on reschedules and cancellations far more often than on the initial booking. I key two-way sync on the appointment ID, so a reminder never fires on a slot that has moved.

Duplicates are a data-model problem, not a workflow problem. If dedup lives inside the automation, every new entry point re-creates them.

Stack I work with daily: n8n, Make, Airtable, REST APIs and webhooks, Claude and OpenAI APIs, WhatsApp Business API, code steps in JavaScript. Close CRM I have not used; the shape is familiar and I would not pretend otherwise.

Remote from Casablanca, same working hours as Western Europe, French, English or Arabic. Happy to start on a paid debugging task rather than a call, if that is a faster way for you to judge.

Jamal

39

Hi Nicolas,

This matches my background in Python and API services, SQL, webhooks, Docker, Kubernetes, and automation. I can help debug n8n, Make, or Zapier workflows, trace webhook payloads, normalize CRM and Airtable data, add idempotent retry and error paths, and document recurring fixes so the system becomes easier to maintain. I am based in Bengaluru, can overlap with European working hours, and am available immediately.

Relevant work: OpenLLM, an OpenAI-compatible Python gateway with runtime management and telemetry: GitHub - Shubhampandeysp01/openllm · GitHub

I am happy to start with a small debugging task and continue at $30/hour if the fit is good.

40 
Hi Nico — this is squarely what I do: debug, maintain, and improve n8n automations connected to CRMs and databases via webhooks and REST APIs.

Relevant experience:
- Built and maintained n8n workflows for lead intake → CRM: create/update contacts, populate pipeline fields and statuses, dedup records, attach transcripts/notes, with error handling, retries, and logging.
- Comfortable in JS code steps for custom logic, field mapping, and API request/response handling (OAuth + token refresh included).
- Databases: PostgreSQL/SQL and Airtable-style structures; schema cleanup and query optimization.
- Integrations: webhooks/APIs across WhatsApp, Google, forms (Typeform/Calendly-style), and CRMs. I pick up a new tool (Close, ClickFunnels) fast since it's the same webhook/API pattern.

I'm detail-oriented and calm when things break — I like tracing a failing run to the exact node and documenting the fix so it doesn't recur. Good written English, and my mornings (I'm in Brazil, GMT-3) overlap European hours.

I'm looking for exactly this kind of ongoing engagement. I'll also submit the Airtable form. Happy to do a short paid test task so you can see how I work before committing.

— Mateus