Job description We’re a marina and campground with several core systems that need to work together. We’re modernizing how we run the business and are looking for a skilled automation engineer to help us connect our tools, cut out manual work, and keep everything running smoothly. We’ve adopted Make.com as our automation platform and plan to stay on it unless there’s a compelling reason to switch. We’re primarily looking for strong Make.com expertise, but experienced Zapier engineers are welcome to apply — the platforms are similar enough that deep expertise in either one translates well. This is an ongoing, part-time role. You’ll design, build, and maintain automations across our operations, with steady work for the right person. What you’ll build • Bookings & operations — reservation confirmations, scheduling, and internal alerts • Marketing & CRM — lead capture, email sequences, contact syncing, and review requests • AI chatbot integration — connecting our website assistant to bookings, email, and our knowledge base • General automation — streamlining other workflows across the business as needs come up What we’re looking for • Proven, in-depth expertise in Make.com or Zapier, with a portfolio of complex, real-world workflows • Strong experience with APIs, webhooks, and third-party app integrations • Solid grasp of data mapping, error handling, and building reliable, maintainable scenarios • A clear communicator who can recommend the best approach — not just take orders • Dependable and responsive, since this is an ongoing relationship Engagement & rate • Ongoing, part-time • We’ll start with an initial project, with strong potential for continued work To apply Send a brief note covering which platform you specialize in (Make.com or Zapier) and your experience with it, 2–3 examples of automations you’ve built (links or short descriptions — ideally similar to what’s above), and your weekly availability. Bonus points if you’ve worked with hospitality, booking, or small-business tools.

I’m looking for someone to automate my newsletter workflow. I would like to take newsletter language from google docs and have it auto publish to Substack and Mailchimp using Make.com. It must be through make.com.

We operate a licensed Adult Family Home (AFH) in Washington State with 24 residents and a team of approximately 25 staff across caregiving and leaders. We are seeking a professional to help improve our business operations, streamline processes, and support overall efficiency. The ideal candidate will have experience in business operations, management, and process improvement, and be able to work closely with our team to identify opportunities for growth and optimization. Deliverables: All of the following must be delivered for the project to be considered complete: 1. Fully built ClickUp workspace with all spaces, folders, lists, templates, custom fields, and dashboards as specified. 2. Five Make.com scenarios built, tested, and active as specified in Section 5. 3. WhatsApp Business group channel setup guide (naming, keyword conventions, how to add members). 4. End-to-end test documentation — at least one full test run of each workflow showing trigger to task creation to escalation to completion. 5. A short handoff document (1–2 pages) explaining how each Make.com scenario works, where to find it, and how to update it if a workflow changes. 6. A 30-minute walkthrough call with our leadership team upon delivery. Required: • Demonstrated ClickUp workspace builds (portfolio required) • Make.com scenario building with conditional logic and email parsing • WhatsApp Business API or Cloud integration experience • Experience with multi-step automation flows • Ability to work from a written SOP / workflow spec • Clear English communication — async updates expected Nice to have: • Experience with healthcare or residential care operations • Experience building ClickUp dashboards for leadership teams • Prior work with email parsing + webhook routing in Make.com • Experience with HIPAA-adjacent data handling This is a build project, not a consulting project — we have defined what we need. We are not looking for someone to redesign the architecture.

We are building a multi-step workflow automation for a healthcare-adjacent B2B service. The automation needs to pull structured data from a web portal, pass it to an AI API to generate personalized documents, route the output through a HIPAA-compliant email delivery platform, and log results for quality review. We are looking for a US-based developer experienced with Make.com or n8n and comfortable working with REST APIs. This is a fixed-price project with a clear scope document provided after an NDA is signed. Please share relevant portfolio examples of similar automation builds.

Overview Transit & Flow is a fast-scaling Columbus home services company (plumbing, HVAC, drain, sewer, water heater, sump pump) building a premium, AI-powered operation. We are wiring together a set of best-in-class platforms into one self-functioning system that captures, books, reschedules, reminds, invoices, and follows up with customers automatically across phone, website chat, and Thumbtack. We need a senior integration specialist to stand this up cleanly, end to end, on a short-term contract. This is an execution role for someone who has built production voice-AI and automation systems before, not a learner. Detailed architecture blueprints will be provided to the hired contractor under NDA. What you will build A connected stack with no manual re-entry between systems: • Bland AI voice agents (several agents: inbound scheduler, after-hours and emergency handling, Thumbtack lead agent, and an outbound reminders and follow-up agent) • A website chat agent running the same booking logic in text • Thumbtack Live Connect bridged to a Bland agent via API and webhook, plus the Thumbtack lead feed into our automation bus • Quo.com as the telephony and SMS layer (call forwarding to Bland, SMS send via API, one consistent business number) • GoHighLevel CRM integration (contact sync, pipelines, nurture) • Make.com as the orchestration layer (scenarios for booking, rescheduling, reminders, estimates, invoicing, lead intake, error handling) • Scheduling, rescheduling, cancellation, and automated appointment reminders against our field service management platform (currently Jobber, migrating to OctopusPro, so platform-flexible API work is required) • Email automation including emailing and resending invoices and receipts on request Core responsibilities • Configure Bland pathways, custom tools, and webhooks that read and write to our systems mid-call (check availability, book, reschedule, cancel) • Build robust Make.com scenarios with idempotency, retries, error handling, and alerting • Integrate REST APIs and webhooks across Bland, Quo, GoHighLevel, Thumbtack, the FSM, and email • Bridge Thumbtack Live Connect to a dedicated Bland number so leads are answered live • Implement automated SMS and voice reminders with confirm and reschedule handling • Document everything and deliver a clean handoff so the system is maintainable and scalable Must-have skills • Proven production experience with a voice-AI platform: Bland strongly preferred, or Vapi, Retell, or Synthflow with transferable skill • Advanced Make.com (or n8n) including webhooks, data stores, error handling, and routing • Strong REST API and webhook integration skills, JSON, authentication, signing • GoHighLevel API experience • Telephony and SMS concepts: call forwarding, SIP or number routing, A2P • Ability to design for scale and reliability, not just a demo that works once Nice to have • Quo.com or comparable VoIP platform experience • Thumbtack pro tooling or lead-response automation experience • Home services or field service management background • OctopusPro, Jobber, or similar FSM API experience Engagement • Short-term contract, estimated 3 to 5 weeks • Milestone-based fixed price preferred, hourly considered for the right expert • Async daily updates, a few live working sessions per week • NDA and scoped system access required; you will not receive owner credentials How to apply Do not send a generic proposal. Answer these in your application: 1. Link or describe a voice-AI agent you built that booked or scheduled against a live external API mid-call. What platform, what API, what was the hardest part? 2. How do you make Make.com or n8n scenarios idempotent and resilient to duplicate webhooks and failed calls? 3. In two or three sentences, how would you bridge Thumbtack Live Connect to a voice AI agent so the agent answers the lead live? 4. Your proposed milestone breakdown and realistic timeline for the scope above. 5. How you handle client credentials and secrets securely. Strong applications that show real systems thinking move to a short paid test task before the full award.

I am looking for a developer to build an automated email outreach system to pitch my music to independent radio stations. Requirements: Connect a database (Google Sheets or Airtable) to an email API (like Mailgun, Brevo, or Amazon SES). Create a template system that dynamically inserts personalized fields (Station Name, Director Name, Genre). Implement safe-sending protocols, including randomized delays (30-90 seconds) between emails to prevent spam flags. Assist with domain configuration (SPF, DKIM, DMARC) to ensure high inbox deliverability. Preferred Tech: Python or No-Code (Zapier/Make.com).

Project Overview: We are a Pool & Spa chemical manufacturing company with a significant amount of physical inventory ready for wholesale distribution. We are currently implementing a headless commerce architecture. While our lead API architect handles the checkout and ERP integration, we need a dedicated Method:CRM specialist to build our outbound B2B sales trigger. Your objective is to execute a clean "Mechanism Dialysis"—separating our B2B wholesale prospecting workflows from our standard accounting contacts, and building the UI triggers to launch automated SMS sequences via our VoIP provider (Quo). The Mission (Scope of Work): You will be working entirely within Method:CRM (and potentially Make.com) to build the following pipeline: 1. Tagging Architecture: Create and structure custom tags (e.g., B2B Prospect - Quo SMS Drip) so we can safely import cold wholesale prospects without corrupting our primary QuickBooks sync data. 2. UI Customization: Build a custom action button on the Method:CRM Contact screen (e.g., "Initiate Quo Sequence"). 3. Webhook Trigger: When that custom button is clicked, Method must fire an outgoing webhook containing the contact's First Name and Mobile Phone number. 4. Routing: Ensure that webhook properly routes (likely via Make.com) to trigger our pre-written SMS sequence in Quo. Required Tech Stack Experience: • Method:CRM (Screen customization, custom actions, and tagging) • REST APIs & Webhook generation • Make.com / Zapier logic • B2B CRM Architecture The Ideal Candidate: I am a firm, results-oriented business owner who values integrity, direct communication, and stewardship of time. I work long hours overseeing manufacturing, so I do not have time to micromanage this build. I need a confident, structural thinker who knows exactly how to manipulate Method:CRM's UI and automation engine. I do not want fluffy agency pitches. I want a sharp, efficient builder who can get in, wire the plumbing, test the webhook, and get out. To Apply: Please start your proposal with the phrase "CRM Dialysis." In your proposal, give me a brief, 1-2 sentence explanation of how you typically handle outgoing webhooks from Method:CRM. Do not send a generic cover letter.

I am looking for an experienced Make.com automation/integration specialist with strong QuickBooks Online experience to build and complete a TrackOps to QuickBooks Online integration for my three businesses. This is not a simple “push an invoice from one system to another” project. The integration needs to handle real accounting workflows accurately across three separate companies using one centralized Make environment, with each company maintaining its own isolated TrackOps and QuickBooks Online account. I have already gone through unsuccessful contractor attempts on this project, so I want to be very clear up front: I am looking for someone who can actually build, test, and demonstrate working functionality in my environment - not someone who can only write a polished proposal. ________________________________________ Business / System Environment You will be working with three separate operating companies: • Megalodon Executive Protection Firm, LLC (EP) • Megalodon Private Investigations Firm, PLLC (PI) • Megalodon Regulatory Advisory Firm, PLLC (RA) Each company has: • its own TrackOps account • its own QuickBooks Online account The integration will be built in one centralized Make environment, but all company data must remain fully isolated by entity, with no crossover between businesses. TrackOps is my operational system of record for: • cases / jobs • customers / clients • invoices • time tracking / hours • mileage / expenses QuickBooks Online is my accounting system of record. The goal is for TrackOps activity to flow into QuickBooks Online with proper accounting treatment and minimal manual re-entry, while preserving clean books and reliable reporting. ________________________________________ Scope of Work I want this project structured into fixed-price milestones that align with the phases of work. A proposed structure is below, but I am open to reasonable adjustments if the contractor has a better recommendation. Milestone 1 – Discovery, Audit, and Foundation • Audit any existing Make scenarios / prior contractor work and document what is reusable versus what should be rebuilt • Review TrackOps API and webhook coverage for all required objects • Review and validate QuickBooks Online chart of accounts, products/services, classes, and other mapping structure relevant to the integration • Review my existing account mapping and identify any structural issues that need to be addressed before the build proceeds • Establish customer sync from TrackOps to QuickBooks Online • Implement duplicate prevention and standardized naming logic Milestone 2 – Core Invoicing, Payments, and Retainers • TrackOps invoices flowing into QuickBooks Online • Correct service / product mapping • Sales tax handling at the invoice line-item level • Payment recording and application to the correct invoice • Retainer handling logic: o retainer receipts booked properly o retainers applied against invoices---in TrackOps---as work is performed o clean accounting treatment in QBO Milestone 3 – Expense / Reimbursement Accounting • Client reimbursable expenses flowing correctly into QuickBooks Online • Administrative fee / markup logic where applicable • Mileage handling from TrackOps into QuickBooks Online • Travel / transportation reimbursement scenarios • Credit memos, debit memos, refunds, and related accounting treatment • Proper payable / reimbursement treatment for contractors or employees Milestone 4 – Profitability, Classification, and Delivery Logic • Case / engagement ID flow into a QuickBooks Online project field • Class / department mapping where appropriate • Product and service mapping refinement • Invoice delivery / emailing logic if included in the final design • Any related workflow needed to support cleaner engagement-level profitability reporting Milestone 5 – Payroll / Time Tracking / Contractor Payment Integration This phase is very important and needs to be approached carefully. TrackOps has a time tracking feature that captures hours by worker. I need the contractor to determine the maximum extent to which TrackOps time can be pushed into QuickBooks Online payroll-related workflows and records. I understand that QuickBooks Online does not permit outside developers to fully automate the final payroll run itself. I am not expecting a fully hands-off payroll run if Intuit’s restrictions do not allow it. However, I do expect this portion of the project to be taken as far as it can reasonably go. The goal of this phase is to automate as much of the payroll preparation workflow as possible, including where feasible: • TrackOps time flowing into QuickBooks Online payroll-related records, hours, or staging data • Worker-level time mapping by employee and/or contractor • Support for hourly payroll workflows to the maximum extent QuickBooks Online allows • Any feasible employee / contractor sync elements between TrackOps and QuickBooks Online • Any feasible support for workers compensation code mapping • Any feasible support for contractor / 1099 payment workflows • Clear identification of what can be automated versus what must remain manual due to Intuit limitations The final payroll run inside QuickBooks Online may remain a manual step, but the integration should be designed so that payroll preparation is automated as far as QuickBooks allows. I also want test runs performed during this phase so the payroll-related functionality can be verified. If something is not possible because of Intuit restrictions, I want that documented clearly, along with the maximum automatable portion and the manual procedure required to complete the payroll process. I do not want anyone overpromising payroll automation that QuickBooks Online will not allow. I do want this portion of the build pushed as far as it can reasonably go and verified with testing. Milestone 6 – Replication to PI and RA Once the Executive Protection build is functioning correctly, replicate the completed build to: • Megalodon Private Investigations Firm, PLLC • Megalodon Regulatory Advisory Firm, PLLC This includes: • adjusting services, accounts, and workflow logic as needed for each entity • maintaining full isolation of data and workflows between all three businesses • validating that each replicated build functions correctly in its own environment Milestone 7 – Testing, Error Handling, Documentation, and Handoff • End-to-end testing across all scenarios • Error handling and failure alerts so issues do not silently fail • Written documentation / runbook • Loom walkthrough or live walkthrough of the final system • Explanation of how to maintain the system and understand failures • Final handoff only after the system is functioning and verified ________________________________________ Required Skills / Experience Please do not apply unless you have real experience with the following: • Make.com automation builds • QuickBooks Online integrations • Accounting-aware workflow design, not just general automation • Invoices, payments, retainers, reimbursements, credits/refunds • Multi-step field mapping and debugging • API/webhook-based integration work • Multi-company / multi-account workflow organization Strong preference if you have experience with: • service businesses • legal / investigations / field services / case management style workflows • profitability / project / class tracking in QBO • payroll-related QBO integration limitations ________________________________________ Deliverables I expect the contractor to deliver working functionality, not just recommendations. That means: • functioning Make scenarios in my environment • correct mapping and accounting treatment • testing and proof of function • clear documentation of what was built, what is partially automated, and what remains manual due to platform limitations • professional communication throughout the project ________________________________________ Critical Milestone Verification Requirement This is extremely important. No milestone will be considered complete until the contractor demonstrates the work live and I verify that the milestone deliverables are functioning in my actual environment. For each milestone, I will require: 1. A live walkthrough / demonstration of the functionality 2. Proof of the actual Make scenarios and workflow logic 3. Proof that the workflow works in my environment 4. My confirmation that the milestone deliverables for that milestone have been satisfied Milestone payment will only be released after verification and acceptance. If you are uncomfortable with that, please do not apply. ________________________________________ Communication Expectations I value direct, professional communication. I do not need constant meetings, but I do need: • acknowledgment of questions • status updates when something is blocked • honesty if something is not possible • no disappearing • no vague milestone claims without proof If there is a technical limitation, I want it surfaced early and clearly. ________________________________________ Prior Contractor Experience / Expectations Going Forward I want to be transparent about why I am being very specific about communication and milestone verification. I have already had two unsuccessful contractor attempts on this project. In one case, the contractor struggled to communicate clearly and directly about the work. I made multiple requests during the engagement that every question I asked be answered clearly, directly, and in a timely manner. Even after I raised that issue more than once, I still was not getting clear answers to straightforward questions about project status, functionality, and next steps. Because communication and responsiveness are essential on a project like this, I ended that engagement. In another case, a contractor submitted a milestone payment request claiming a milestone was complete, but when I attempted to verify the work through a live walkthrough and demonstration, the contractor could not clearly demonstrate that the functionality had actually been built and working in my environment. That engagement was also terminated. I am not including this to be dramatic or difficult. I am including it so expectations are completely clear from the beginning. For this project, I need a contractor who can do all of the following consistently: • answer questions clearly, directly, and in a timely manner • communicate honestly about what is done, what is not done, and what is blocked • demonstrate completed work live before requesting milestone payment • surface technical limitations early instead of overpromising or avoiding direct answers If your communication style is vague, delayed, or indirect, or if you are not comfortable demonstrating completed work before requesting payment, then this project is probably not a good fit. ________________________________________ Proposal Instructions If you apply, please include the following: 1. A short explanation of your experience with Make.com and QuickBooks Online integrations 2. Your recommended milestone pricing for the milestone structure above ________________________________________ Budget / Engagement Structure I am open to fixed-price milestone proposals for the full project. I prefer to structure the engagement in multiple milestones rather than one large payment. I am open to contractors proposing their own pricing by milestone, but I want the proposal structured around the milestone framework above or a clearly justified alternative.

I am building a reusable lead follow-up and consultation booking automation system for med spas and aesthetic clinics. I need an experienced automation specialist who can build, test, document, and hand off a production-ready workflow system. This is not a one-off Zapier task. I need a reusable system that can be adapted for future clients. What the system should do: * Recover missed calls and website inquiries before they go cold * Send fast SMS/email follow-up to new leads * Collect basic service interest without giving medical advice * Send a consultation booking link * Log every lead in a CRM or lead tracker * Track lead status from new inquiry to booked consultation * Notify clinic staff when a lead replies, books, or needs human review * Escalate medical, treatment-specific, pricing-sensitive, or sensitive questions to staff * Run a simple no-response follow-up sequence * Send appointment reminders after a consultation is booked * Provide a weekly lead activity summary showing new leads, contacted leads, booked consultations, no-responses, and escalations Preferred stack: - Make - Airtable - Twilio - Calendly - Google Workspace / Gmail I am open to GoHighLevel or other stack recommendations if you can explain the trade-offs clearly. Important compliance guardrails: The system is for appointment scheduling and lead follow-up only. It must not provide medical advice, diagnose, recommend treatments, collect sensitive medical history, or answer treatment-specific questions. Any medical, pricing-sensitive, treatment-specific, or sensitive question should be routed to clinic staff. Required deliverables: - Workflow diagram - Recommended stack document - Working demo system - CRM/tracker template - SMS/email message templates configured with variables - Testing checklist - Client onboarding checklist - Duplication/setup guide - Loom walkthrough - Handoff documentation - Monthly tool cost estimate - Limitations and risks document Budget: Fixed price: $1,500 Budget flexible up to $2,000 for the right reusable system. Proposed milestones: Milestone 1 — Architecture and stack recommendation $300 Milestone 2 — Working build $800 Milestone 3 — Documentation and handoff $400 PLEASE COMPLETE THE SCREENING QUESTIONS WHEN APPLYING: 1. Describe a workflow you built involving SMS follow-up triggered by a call or form submission. What tools did you use? 2. What is the most complex Make.com scenario you have built? 3. Have you built Airtable as a CRM or lead tracker before? Describe the structure. 4. Have you integrated Twilio with Make or Zapier for SMS automation? 5. Have you connected Calendly webhooks to downstream automation? 6. How would you prevent this system from giving medical advice or collecting sensitive information? 7. What does your documentation and handoff process include? 8. For this use case, would you recommend GoHighLevel or Make + Airtable + Twilio? Why?

We're a talent partnerships agency looking for an experienced Airtable and automation expert for an ongoing, flexible retainer role. We need a true problem-solver who looks at our entire business and workflow and designs smart, simplified solutions, not someone who just builds exactly what's asked without considering the bigger picture. We have a high-volume database (300k+ records) with multiple datasets that aren't perfectly connected, and we're running a multi-phase plan to enrich, connect, and automate across all of it. *Immediate project (starting now): Integrating two third-party data APIs into Airtable: - Apollo: ongoing contact enrichment using job-change detection to push updates into staging columns automatically, plus enrichment on new contacts. The more straightforward of the two. - Winmo: pulling verified brand, contact, and agency-to-brand relationship data, matched to our existing records via stored IDs. More involved, since it requires linking incoming data to the correct existing records (some as linked records) rather than creating duplicates. Both feed into staging columns alongside our existing data, with a review-and-approve step before anything updates our live records (non-destructive enrichment). Larger phased plan (where the long-term role goes): The APIs are just the start. From there we're building toward AI-powered data enrichment across our full database, an automated outreach and follow-up system modeled on one we already run, and ongoing automation and workflow optimization across the board. We want someone who can own this roadmap with us, bring expertise we don't have in-house, and simplify a complex system rather than add to it. What we're looking for: - Strong Airtable expertise: analysis, troubleshooting, architecture, and workflow strategy, not just automation building - Strong Make (Integromat) and Zapier experience (required) - Third-party API integration experience (required) - Experience with AI/LLM API integration (OpenAI or similar) and structured data workflows (strongly preferred) - Webflow experience (a plus) - Someone who delivers polished, end-to-end solutions and thinks about the whole workflow, so we're not stuck making endless adjustments down the line - A genuine collaborator who brings ideas and expertise, rather than relying on us to design the solution and just executing it Important on pricing: We're looking for someone who quotes a flat fee per project upfront, based on your own hourly rate and time estimate, rather than billing open-ended hourly. For ongoing support we'd set up a retainer. This structure matters to us, so please confirm you're comfortable working this way. This is a reliable, long-term relationship for the right person, with steady work across data enrichment, AI, and automation. Please share relevant experience with similar Airtable, API, and automation projects, and how you typically structure project versus retainer pricing.