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

Jobs
1

Hey everyone,

we’re hiring a hands-on Sales Tech & Automation Specialist for ongoing remote work.

We run a sales agency and need someone technically talented who can help us debug, maintain, and improve our systems.

Sales experience is not required. We’re mainly looking for someone who enjoys building systems and solving technical problems. Experience in sales operations would be a plus.

This is not a one-off project. We are scaling and want to bring in someone who can become a long-term part of the team. If the culture and skillset fit is strong, this role can grow into broader technical ownership and potentially leading a small tech operations team down the line.

Stack:

  • Close CRM or other sales CRMs

  • n8n / Make / Zapier

  • Airtable / SQL databases

  • Calendly

  • Typeform

  • ClickFunnels

  • Webhooks / APIs

  • JavaScript or code steps are a strong bonus

Typical work:

  • Debug broken automations

  • Maintain CRM fields, pipelines, statuses, smart views, and workflows

  • Build and improve systems

  • Optimize databases

  • Connect tools through n8n, webhooks, and APIs

  • Document recurring issues and suggest system improvements

  • Communicate clearly with our team in Slack

Good fit:

  • Strong technical problem solver

  • Detail-oriented and calm when something breaks

  • Comfortable debugging messy client workflows step by step

  • Good written English

  • Some overlap with European working hours; our clients are mostly based in the US

  • Looking for ongoing work, not just one-off projects

Apply here:

Looking forward to hearing from you.

Nicolas

8 Likes
2

Nicolas, this is very close to my lane: keeping n8n/Make/Zapier + Airtable/SQL + CRM handoffs from breaking quietly, then leaving enough notes that the sales team can keep moving.

I’m Brazil/GMT-3, so European-hours overlap is partial but usable. Before I put the full application into Airtable: are you open to a long-term remote contractor from Brazil, or are you only screening for closer EU coverage?

3

Hey Nico, Misha here — n8n and AI automation developer. I read your post and this sounds exactly like the kind of ongoing technical ownership I deliver. I’d handle debugging broken automations, maintaining CRM pipelines and smart views, and connecting tools like Close, Airtable, and Typeform through n8n webhooks and APIs. I’m comfortable writing code steps in JavaScript or Python when no-code alone falls short, and I keep everything documented and logged so nothing stays broken twice. You get someone who thinks in systems, not just tickets. Portfolio: https://mikedevai.netlify.app/ | Telegram: Telegram: Contact @hely_chatbots | WhatsApp: +375293761570

4

Hi Nicolas, this is exactly the work I do, keeping a sales agency’s CRM and n8n automations running so they do not quietly break, with clear notes so your team keeps moving. I’m comfortable across Close and other CRMs, n8n and Make, Airtable and SQL, and webhooks and APIs, and I stay calm and methodical when something breaks, I debug messy workflows step by step instead of guessing. I’m US based, so I line up well with your mostly US clients. I’d start with one scoped task, like auditing and fixing your current broken automations and documenting them, so you can see how I work before the ongoing role.

Quick question, what is breaking most often right now, and which CRM are you on? Happy to send a 90 second Loom of how I approach a broken workflow.

5

Hi Nicolas,

I’m a technical problem solver, not a salesperson, which fits exactly what you’re looking for.

My experience:

  • n8n automation (building + fixing workflows)
  • SQL / Supabase databases
  • API & webhook integrations
  • Debugging broken or messy systems

Why I’m a fit:

  • I’m calm under pressure when things break
  • I document issues so they don’t repeat
  • I write clear English and communicate well in Slack
  • I’m looking for long-term work, not one-off projects
  • I can overlap with European hours while supporting US clients

I’d love to start with a small trial task so you can see how I work before committing to anything bigger.

Best,
Samuel

6

Hi Nicolas,

This role fits me well. I’m a technical problem-solver who enjoys building and fixing systems, and I work mainly async through written communication (Slack), so the day-to-day here suits me.

I’m an AI/automation engineer and full-stack developer, and my stack overlaps directly with yours:

  • n8n (production workflows), webhooks and REST APIs — my core tools
  • JavaScript/TypeScript and custom code steps (the “strong bonus” you mention)
  • CRM maintenance and integration via API — I’ve built and maintained CRM workflows (amoCRM, Bitrix24); Close CRM is API-driven, so I can ramp quickly
  • SQL databases and optimization, plus connecting tools like Calendly, Typeform and ClickFunnels through webhooks/APIs

I stay calm and methodical when things break: I debug messy workflows step by step, find the root cause, fix it, and document recurring issues so they don’t repeat — and I tend to suggest system improvements rather than just patch over them.

I’m specifically after ongoing work, not one-offs, and the path you describe — growing into broader technical ownership — is exactly what I want to build toward.

Availability: 20–40 hrs/week, flexible. I’m async-first via Slack and can comfortably overlap with European morning hours.

Work samples: portfolio at qadam-tech.lovable.app, and a short video where I break down AI-agent architecture on my YouTube — youtube.com/@qadamtech

Instagram: qadamtech
Looking forward to it.
Rashid — Qadam Tech
gorlum06@gmail.com

7

Hi Nico,

this looks like a strong match. We’re Avialdo Solutions, an AI automation delivery agency.

We work with sales agencies on exactly this stack: Close CRM, n8n, Airtable, SQL databases, Calendly, Typeform, webhooks and APIs. We debug broken automations, maintain CRM workflows, build improvements, and document recurring issues - the full scope you described.

We’re a team rather than one person, so coverage is consistent and there’s no single point of failure as you scale. Long-term retainer is our preferred model too.

Happy to jump on a quick call to see if the fit works. DM me or reply here.

8

Hey Nico, this sounds like the kind of sales-ops work where reliability matters more than adding more automations. I’d start by finding the workflows that break most often, the CRM fields/statuses the team depends on, and the handoffs that slow people down every week. Clean those first, then improve the bigger system around them. If helpful, I can share the audit checklist I’d use for a Close/Airtable/n8n style stack.

9

For an ongoing role like this, I would suggest starting with one small paid trial task so both sides can test fit before committing to a bigger working relationship.

A useful first task could be:

- pick one sales ops workflow that currently breaks or wastes time

- map the trigger, data fields, and destination

- normalize the payload

- add one error log and one alert path

- document what changed and what still needs production access

I prefer sample/redacted data for the first pass and buyer-owned credentials for live systems. That keeps the first task low-risk while still showing whether the working style fits.

10

Hi Nicolas, this kind of role usually benefits from a small breakage inventory before anyone starts changing workflows.

For the stack you listed, I would triage it in three layers:

  1. CRM / Airtable fields: which field is the source of truth, and which views/statuses are downstream only;
  2. automation handoffs: which n8n / Make / Zapier step first changes or drops the payload;
  3. documentation: which recurring failures need a runbook so the team does not re-debug the same issue.

A useful first artifact could be a short workflow-breakage triage note: broken path, likely failing handoff, owner system, and the smallest test to prove the fix.

No credentials, tokens, payment data, or account access would be needed for that first pass; redacted screenshots/workflow descriptions are enough.

11

Hi, this looks close to the kind of systems work I can help with: debugging workflows, tightening CRM/database routing, and making automations easier to maintain.

For a trial task, I would keep it narrow: review one live CRM/workflow issue, trace the data path, add basic logging/error notes, fix the smallest broken part, and leave a short handoff doc. I recently built a support automation demo with intent routing, handoff logic, tests, and docs, so I can show how I approach reliability before scaling a system.

If you are still evaluating people, I am happy to start with a small paid 48-hour trial so fit is easy to judge.

What CRM/database stack are you using right now?

Sanskar

12

Hey,

Sounds like you need someone who keeps the sales stack running and stays calm when something breaks at the worst possible moment — that’s genuinely the kind of work I enjoy.

I build and maintain automations that connect tools through webhooks and APIs, keep CRM data clean (pipelines, fields, statuses — the stuff that quietly rots when no one’s watching), and treat the database as the backbone rather than an afterthought. The part most people skip, and the part that actually stops problems from recurring, is documentation — so I write down every repeat issue and how it was solved.

A concrete example: I built an order-processing system that takes orders in via webhook, validates and prioritizes them, syncs everything to a database, and alerts the team in real time. That’s the same webhook → logic → CRM/DB → notification pattern your stack runs on, just in a different industry.

I also run my own self-hosted n8n in production, including the unglamorous side — error handling, retries, alerts, and untangling messy flows step by step when they break. So debugging someone else’s “why did this suddenly stop working” is familiar territory.

Honest about the stack: my main CRM is HubSpot rather than Close, and my database work is Google Sheets plus a MySQL database I run for my own store. The patterns map directly and I pick up new tools fast. I also write JavaScript in code steps (and some Python) when the standard nodes aren’t enough.

I’m in Ukraine — good overlap with European hours and part of the US day — I communicate clearly in written English, and I’m specifically after ongoing work, not a one-off.

If it helps you judge fit, I’m happy to start small: take one of your broken or messy automations, fix it, and document it, so you can see how I work before anything long-term.

— Pavlo

13

Hi Nicolas, this lines up closely with what I build: I run a production n8n system handling lead capture, conditional routing, CRM logging (Google Sheets), automated follow-ups, and reply detection — webhooks, APIs, and error handling throughout. Airtable, Close CRM, Calendly, Typeform and ClickFunnels would be new for me specifically, though the pattern (webhook in, map fields, push to CRM) is the same architecture I already run. I’m based in Benin (UTC+1) — solid overlap with European hours, more than most LATAM-based candidates. Happy to share a walkthrough of what I’ve built if useful before the form.

14

Hi Nico — this fits me well; I’m the “enjoys building systems + solving technical problems” type, and I’ve worked hands-on across your exact stack.

What I’d bring day one:

• Close CRM + n8n/Make/Zapier: audit your current automations, fix the brittle parts, and rebuild the critical flows properly (webhooks/APIs, proper error handling + retries) so they stop breaking silently.

• Data: Airtable + SQL for clean single-source reporting; JS/code steps where no-code hits its ceiling.

• Funnel plumbing: Calendly / Typeform / ClickFunnels wired end-to-end into the CRM so lead → booked → nurtured is automatic and traceable.

I like owning systems long-term, not just shipping and disappearing — so the “grow into broader technical ownership” path is exactly what I’m after too.

Availability: can start immediately, flexible for remote. Happy to do a quick paid trial task first (fix one broken flow, or build one you need) so you see the quality before committing to ongoing work.

Quick question: what’s the most painful or broken part of your stack right now? Tell me and I’ll show you exactly how I’d fix it.

— Lucas

15

Just submitted my application via the form — CET-based, Make.com daily and porting to n8n, looking forward to hearing from you.

16

Hi Nico,

I saw your post looking for a Sales Tech & Automation Specialist and wanted to apply. I specialize in connecting front-end sales pipelines to backend databases and CRMs using n8n, Python, and SQL/DBMS.

My technical background perfectly aligns with managing ongoing data architecture and sales systems:

  • Lead Gen & Database Automation: I engineered an end-to-end n8n workflow that automatically extracts, cleans, and organizes inbound business leads from multiple sources directly into relational database systems and Google Sheets.
  • Data & API Manipulation: Highly proficient in using Python (Pandas/NumPy) inside n8n to handle complex data payloads, map API webhooks, and prevent data duplication across systems.
  • Relational Databases (SQL): Deep understanding of database schemas and ERD designs, ensuring data flowing from your CRMs is cleanly structured and easily searchable.

I work remotely and am ready to support your systems long-term. To make this zero-risk for you, I am open to executing a small, paid test workflow this week so you can check the clean structure of my n8n logs and data maps.

Are you free for a quick message exchange or 10-minute Zoom call to discuss the current CRM architecture you need automated?

Best regards,
Hisham Said

17

I applied through the form Wednesday. Since then I diagnosed a false positive in my production eval suite, fixed the harness, and verified 16/16 green. That’s the debug-and-document work your post describes. Still interested. I can walk through any of it live: elyptis.ai

18

Hi, one honest note first: I’m not looking for a team role, so if you specifically want an in-house hire, ignore this.

If you’d consider it as an ongoing service instead, that’s what I do, and for a sales agency it often works out cheaper than a hire. The work you describe (debug broken automations, keep CRM fields, pipelines and workflows healthy, build new ones) is what I run as a monitoring retainer: errors alert me before your team notices, small breaks get fixed the same day, and you get a monthly note on what broke and what changed.

The thing I’d fix first in a stack like yours: most Close/Zapier/n8n setups fail quietly. A field gets renamed in the CRM, or an API version bumps, and the automation keeps “running” while records stop syncing. Nobody finds out until a rep asks where a lead went. Every workflow I take over gets an error path that alerts with enough context to know what broke without opening the tool, plus retries on the external calls.

Happy to start with a paid audit of what you have so you can see how I work before committing to anything ongoing.

19

Hi Nicolas, is this role still open? My current work centres on diagnosing and repairing unreliable n8n workflows involving email, Sheets/CRM systems, APIs, AI processing and human approval. Happy to start with one small paid trial task.

20

Hi Nicolas,

I just submitted the Airtable form.

This role matches my current focus: n8n/Make-style workflow automation, CRM/API integrations, SQL-backed data flows, and debugging messy automation systems.

Relevant work:

I’m especially interested in the ongoing maintenance/debugging side, not just one-off workflow builds.

Best,
Yingqiang