Hiring: Make.com specialist with MindBody API experience

Hi Make community,

We’re a study skills and executive function coaching center in McLean, VA looking to hire a Make.com specialist for an ongoing engagement. We have a well-mapped set of automation scenarios ready to build — we just need someone to build them.

Our stack: MindBody (hope to use StartIntegrate/MAXMEL connector), HubSpot, Google Workspace , ActiveCampaign, Eventbrite, Trainual, Airtable, Zoom.

We also use Appiant to sync MindBody and HubSpot contact records — any scenarios must work alongside that existing integration for now.

The test project (paid):
When a student purchases a course in MindBody, trigger a Make scenario that: (1) checks existing MB enrollments and adds them to any missing sessions, (2) updates a HubSpot contact property, (3) adds them to the correct HubSpot segment, (4) appends a row to a Google Sheet, (5) alerts a VA for a conditional follow-up step, and (6) sends a confirmation email from a HubSpot template. As much of that as we can automate is a plus.

After the test project, we have a prioritized list of builds: holiday procedure automations (8+ parallel actions per holiday triggered from a Google Sheet), staff onboarding/offboarding cascades, coach assignment → HubSpot list sync, email parser → Airtable, and more.

Hard requirements:
— Real MindBody API experience, specifically with the StartIntegrate/MAXMEL connector
— Make.com only (not Zapier or n8n)
— Full documentation with every build
— US EST hours overlap a plus

To respond, please share: have you built with the StartIntegrate MindBody connector before? If so, describe what you built. And how would you approach checking a client’s existing class enrollments in MindBody before adding new ones? What is your fee?

We’re ready to move quickly and have a detailed spec document ready to share.

Debbie from The StudyPro

www.thestudypro.com

2 Likes

Hi @StudyPro , your test project spec is refreshingly clear this is exactly the kind of multi-branch build Make handles well.

For the enrollment check, I’d hit the StartIntegrate connector to pull the student’s existing MB class visits first, then run a Router with a filter comparing enrolled session IDs against your course’s required sessions only the missing ones proceed to the enrollment call, avoiding duplicates. From there it’s a clean fan-out: HubSpot property update, segment add, Sheets append row, a VA alert via conditional path, and the templated confirmation email. Appiant’s sync stays untouched since we’re reading/writing distinct fields.

I build MindBody-Make integrations regularly and document every scenario happy to take this on and share my rate after seeing your spec.

───

Website: https://www.pathfinderautomationsolutions.com

Upwork: https://www.upwork.com/freelancers/pathfinderautomate

Book a call: Calendly

Hi Taiwo,

Thanks for the detailed response — your approach to the enrollment check is helpful, and you addressed the Appiant dependency unprompted which I appreciated.

One question before I share the full spec: your forum post mentions you build MindBody-Make integrations regularly, but I didn’t see any MindBody work in your portfolio. Can you point me to a specific MindBody project you’ve built — what it did, what triggered it, and what tools it connected to?

If you can share that, I’m happy to set up a call.

Thanks,
Debbie

Hey @StudyPro!

The MindBody integrations I referenced were built inside client accounts that I no longer have access to the details are protected under client confidentiality so I’m unable to share specifics publicly.

What I can say with confidence is that the logic you need enrollment checks, conditional session additions, HubSpot syncing, Google Sheets logging, VA alerts, and confirmation emails is well within what I build regularly in Make.com. The test project is a low-risk way to validate that for yourself before committing to the full engagement.

Happy to jump on a call and review your spec whenever you’re ready!

Taiwo

Hi Debbie,

This sounds like a great project and exactly the type of automation work we deliver at Flowbird Ltd.

We’re a UK-based Make Partner, HubSpot Diamond Partner, and ActiveCampaign Partner, with extensive experience designing and implementing complex Make.com automations involving HubSpot, Google Workspace, Airtable, ActiveCampaign, Zoom, and custom API integrations.

We’re also currently delivering a similar automation project for a university, involving student onboarding, enrolment workflows, CRM synchronisation, communications, and operational process automation. While I can’t share specific details, it gives us a strong understanding of the challenges involved in education-focused workflows.

While we haven’t specifically worked with the StartIntegrate/MAXMEL MindBody connector, we have significant experience integrating third-party connectors and APIs into Make.com.

If you’re open to discussing the project, I’d be happy to review your specification document and discuss how we can help. Feel free to DM me or email me at [email protected].

Many Thanks,

Roshan
Flowbird Ltd

This looks like a solid Make.com automation setup across multiple tools, especially MindBody and HubSpot.

Before I go deeper are you already using the StartIntegrate/MAXMEL connector in your current MindBody setup, or is that still being configured?

From what you’ve described, the main focus is to make sure student purchases are correctly synced across systems without duplicates or missing data, while keeping everything stable and scalable.

Happy to take a look at your current setup and jump on a quick call to understand how things are structured right now.

:page_facing_up: Check my profile: https://www.upwork.com/freelancers/farhana401
:telephone_receiver: Book a quick call:Calendly - Automaxion

Hi Debbie,

I’m Christo, a software developer based in Berlin. I haven’t shipped a StartIntegrate MindBody build for a prior client, so rather than describe past work you’d have to take on trust, I built your test project. It’s running here on synthetic student data with no login: https://course-sync-demo.9592.tech. It goes through all six steps of your scenario, and there’s an importable Make blueprint and the full build documentation behind it. You listed full documentation as a hard requirement, so the runbook on that page is also the best sample of how I work.

On checking existing enrollments before adding new ones: the connector can search clients and classes and add a client to a class, but it has no module for a client’s current visits. So that step is a direct GET ClientVisits call for the sessions the student is already booked into, then a router that compares those against the ones the course requires and adds only what’s missing. In the demo a student already in sessions 1 and 2 gets added to 3, 4 and 5, and isn’t re-added to the two they’ve already got.

The purchase trigger needed the same kind of bridge. The connector only fires on new or updated clients, not on a sale, so the “when a student buys a course” step runs off a MindBody clientSale.created webhook into a Make custom webhook, which is the right event for a purchase.

There are two more details that matter for your stack. The HubSpot steps only write to an automation-namespaced property, so they leave the identity fields your Appiant sync owns untouched and the two run alongside each other. And the blueprint uses plain HTTP modules for the MindBody calls, so it imports into any account before the StartIntegrate app is even installed. The documentation shows the native-module swaps for once the connector is live in your setup.

On fee: $300 flat for the test project, finalized and running in your account with full documentation. If it works out for you, I’d price the backlog scenarios flat per scenario once you’ve seen the first one in your account.

I’m in Berlin, so my afternoons overlap your EST mornings. If you click through the demo and something’s off or missing, I’d want to know. Either way it’s there for you to try.

Christo

Hi @StudyPro,

This is one of the clearest project briefs I’ve seen here.

Although I haven’t used the StartIntegrate/MAXMEL connector specifically, I’ve built production Make.com systems involving Google Workspace, Airtable, HubSpot, AI services, APIs, webhooks and multi-step business workflows where reliability and duplicate prevention were critical.

From your description, I’d approach the enrollment flow by first retrieving the student’s current MindBody enrollments, comparing them against the purchased sessions, only creating missing enrollments, then updating HubSpot, appending the audit row, notifying the VA and sending the confirmation email. I’d also make the scenario idempotent so reruns don’t create duplicate records.

A few questions:

• Is the Appiant sync writing both ways between MindBody and HubSpot, or is HubSpot mainly acting as the CRM?
• Are you expecting all enrollment logic to go through the StartIntegrate connector, or are direct MindBody API calls acceptable where necessary?
• Will you be providing a sandbox account for the paid test project?

I’ve also sent you a DM with my portfolio, case studies and contact details if you’d like to discuss the project further.

Hey @StudyPro,

Have sent you a DM as well. I’d love to help as I run an AI studio called Automation Jinn where we help companies leverage AI and automate their processes. I am Make advanced certified and Airtable Certified Builder with a background in computer science so quite comfortable in integrating API and custom code. I have experience working with both SMB’s and large enterprises.

Some of my relevant work-
• For an education company, I integrated LMS with Airtable, Make, and their CRM via API handling complex pagination and syncing data in real time.
• For a fintech startup(raised €8.1M), automated there lead flows in the CRM and built a custom Slack bot to flag churn risks.
• Built a workflow that enriches and qualifies inbound leads using Bright Data MCP while updating the CRM in Hubspot for both qualified and unqualified.

I work more as an AI transformation partner for my clients rather than just a builder. Would love to learn about your day to day operations :slight_smile:

Happy to also jump on a call if it’s easier- 30 Min Meeting | Sparsh From Automation Jinn | Cal.com

Cheers,
Sparsh
Founder
Automation Jinn

Hi! I’m Misha, an automation and LLM integration expert. I can build and document your Make.com scenarios from end to end, integrating MindBody, HubSpot, Google Workspace, ActiveCampaign, Airtable, Zoom, and your existing Appiant synchronization without disrupting current workflows. For the test project, I would design a modular scenario that validates existing MindBody enrollments before creating new ones, updates the appropriate HubSpot properties and lists, logs activity to Google Sheets, triggers conditional notifications for your VA, and sends confirmation emails from HubSpot templates, with comprehensive error handling and logging throughout. While I haven’t worked specifically with the StartIntegrate/MAXMEL connector, I have extensive experience integrating complex APIs, webhooks, and third-party connectors in Make.com, so I can quickly adapt to its implementation and documentation. My focus is on building reliable, maintainable automations that reduce administrative work, prevent duplicate enrollments, and provide a scalable foundation for all of your future workflow projects. My rate is $40/hour, and I’m available to start immediately.

Connect on WhatsApp: +375293761570 | View My Portfolio: https://mikedevai.netlify.app/

Hi @StudyPro,

Are you available for our call? Please let me know if you need me to resend the meeting link or if we should reschedule.

Best regards,

Taiwo Alagbe

Hi Debbie,

Being upfront: I haven’t worked with the
StartIntegrate/MAXMEL MindBody connector
specifically, so I don’t want to claim
experience I don’t have given how central
that requirement is to your build.

What I have built: multi-step Make.com scenarios
with HubSpot updates, Google Sheets logging,
conditional alerts, and templated email
confirmations — which matches most of your test
project outside the MindBody-specific piece.

If you’re open to it, I’d be glad to invest time
researching the StartIntegrate connector
thoroughly before quoting a fee, so I’m not
guessing on the MindBody enrollment-checking
logic. Alternatively, if you need someone with
proven MindBody connector experience specifically
for this first phase, I understand that’s likely
the safer choice for you.

Happy to discuss if there’s a way this could work,
but wanted to be honest about where I stand rather
than overstate my fit.

— Bhumi Solanki
VEDANTIX AI

The constraint that shapes your test project isn’t any of the six steps — it’s the coexistence requirement you stated: whatever the scenario writes must not fight the Appiant sync. That means deciding, field by field, which system is the source of truth, and making the Make scenario idempotent — safe to re-run without double-enrolling a student or overwriting a HubSpot property the sync just set. Step 1 (checking existing enrollments before adding) is exactly the right instinct; the same check-before-write discipline needs to run through steps 2-6 as well.

Being straight with you since you asked another applicant the same question: I don’t have prior MindBody projects to show. What I do have is precisely this kind of multi-system, sync-coexistence plumbing, and the test project is precisely the format that lets you judge that on evidence instead of claims.

I’d take the paid test at a fixed price, delivered with a written run-log showing each step verified against a real purchase.

Async, CET, remote-only, written briefs over meetings.

Hi StudyPro — if you’re still looking for someone with Make.com + MindBody API experience, I may be able to help with the screening process.

I’m testing an early beta called Demandis that matches specific technical problems with people who have relevant experience. I’d be happy to shortlist 2–3 potentially relevant candidates for you at no charge and with no obligation to hire anyone we suggest.

If the role is still open, I’d be happy to learn a little more about the workflows you need built.

Hi, the step that usually breaks this one is the first: checking the existing MindBody enrollments before adding the missing sessions. If that check is not idempotent, a retry after a timeout enrols the student a second time and the scenario still finishes green. I would key the write on the enrollment id instead of appending, so a repeated run leaves the record count unchanged.

I can build the paid test scenario end to end within two business days for USD 80, payable once you have seen it run cleanly on a real purchase.

One thing worth saying upfront: my documented work is in n8n rather than Make, and I have not worked with MindBody before. The branching and the deduplication transfer; the platform is not the one I use every day.

David

Quick update for anyone who finds this thread: we hired Christo Wilken, and I’m glad we did.

We talked to five candidates. Christo stood out because he sent a working demo up front and was transparent about his approach and pricing from day one. Our course registration automation is now live: when a family books a course in MindBody, Make handles the HubSpot segment, adds them to our roster sheet, alerts our VA when there’s a follow-up step, and drafts the confirmation email. That used to be a pile of manual steps for our front desk every time someone registered.

He’s now helping with our staff offboarding automation too. Highly recommend.

Debbie, The StudyPro