Experienced Automation Engineer for API Integration
Budget: $250 – $750 USD
Automation Engineer Needed – Thumbtack, Make.com, OpenPhone/Twilio, Slack (Revenue-Focused)
We are AGeekOnDemand.com, a multi-city on-site IT support business.
This role is focused strictly on income-producing automation, not experiments or blue-sky architecture.
Immediate priority (must be first):
Fix and extend Thumbtack webhooks so all cities (starting with Chicago) trigger auto SMS replies correctly
Ensure inbound/outbound SMS works reliably (OpenPhone for now; Twilio later)
Make sure SMS replies are visible in Slack
Add basic follow-up SMS logic when leads don’t respond
Tech stack (required):
Make.com (strong experience)
Webhooks (design, debugging, retries, logging)
REST APIs (Thumbtack experience is a BIG plus)
OpenPhone or Twilio SMS
Slack integrations (bots, slash commands, or webhooks)
Nice to have (later, not day one):
AI voice or SMS tools (Bland.ai, OpenAI, etc.)
Google Sheets as a lightweight data store
How we work:
Revenue first. If it doesn’t help convert leads, we park it.
Modular builds only (each piece should be able to plug into a future master dashboard)
No over-engineering
No “research billing” without approval
Clear milestones and frequent check-ins with working outputs
Payment structure:
Fixed-price milestones or time-tracked with caps
First milestone must directly impact lead conversion
To apply, you MUST answer these 3 questions:
Describe a webhook → automation → SMS flow you’ve personally built
Do you prefer Make.com or Zapier, and why?
How would you debug a webhook that fires for some cities but not others?
Proposals that don’t answer all three questions will be ignored.
We are AGeekOnDemand.com, a multi-city on-site IT support business.
This role is focused strictly on income-producing automation, not experiments or blue-sky architecture.
Immediate priority (must be first):
Fix and extend Thumbtack webhooks so all cities (starting with Chicago) trigger auto SMS replies correctly
Ensure inbound/outbound SMS works reliably (OpenPhone for now; Twilio later)
Make sure SMS replies are visible in Slack
Add basic follow-up SMS logic when leads don’t respond
Tech stack (required):
Make.com (strong experience)
Webhooks (design, debugging, retries, logging)
REST APIs (Thumbtack experience is a BIG plus)
OpenPhone or Twilio SMS
Slack integrations (bots, slash commands, or webhooks)
Nice to have (later, not day one):
AI voice or SMS tools (Bland.ai, OpenAI, etc.)
Google Sheets as a lightweight data store
How we work:
Revenue first. If it doesn’t help convert leads, we park it.
Modular builds only (each piece should be able to plug into a future master dashboard)
No over-engineering
No “research billing” without approval
Clear milestones and frequent check-ins with working outputs
Payment structure:
Fixed-price milestones or time-tracked with caps
First milestone must directly impact lead conversion
To apply, you MUST answer these 3 questions:
Describe a webhook → automation → SMS flow you’ve personally built
Do you prefer Make.com or Zapier, and why?
How would you debug a webhook that fires for some cities but not others?
Proposals that don’t answer all three questions will be ignored.