Help Needed: Integrate Acuity Scheduling → OrderPort (Customer Sync with API Safeguards)

Hire a Pro
1

Hi everyone —

I’m looking for a Make.com expert to help finalize a connection between Acuity Scheduling and OrderPort using OrderPort’s REST API (UAPI).

The goal is straightforward but needs to be done safely:

  • When a new appointment is booked in Acuity, I want to search OrderPort by customer email.

  • If the email exists → do nothing.

  • If it doesn’t exist → (optionally) create a new customer record only with proper safeguards.

  • Marketing Opt-In field should also pass through if available.

I already have:

  • API credentials from OrderPort (ClientId, ApiKey, ApiToken).

  • Working Base64 authorization key.

  • Scenario partially built in Make (Acuity → HTTP Search → Router → Upsert).

  • I’ve tested the endpoints (/api/customers/search and /api/customers/upsert), but I need help finalizing headers, testing payloads, and ensuring the flow is 100% safe against data overwrites.

Looking for someone who:

  • Has real Make.com experience (router logic, HTTP modules, API headers, filters).

  • Understands Base64 Bearer authentication and REST JSON calls.

  • Can verify the setup end-to-end and ensure OrderPort data integrity.

  • Ideally has worked with CRM or e-commerce APIs (OrderPort, Commerce7, WineDirect, or similar).

Budget: Open to hourly or fixed project depending on scope — this is a small integration but needs to be done right.
Timeline: Ready to start immediately.

If interested, please reply here or DM me with your experience and an estimate.
I can share documentation (UAPI PDF) and screenshots of the current scenario.

Thanks,
Dan

1 Like
3

Hello @3PDan , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

5

Hi Dan,

I am immediately available for assistance.
Please connect further to discuss in details prior initiating

Regards
Deep

6

Hi Dan,

This aligns well with what I’ve been building lately using Make.com and custom API flows: https://hashlogics.com/portfolio. I’ve worked on similar REST-based integrations where we connected booking systems and CRMs via secure HTTP modules — with proper Base64 Bearer authentication, header validation, and router logic to prevent overwrites.

In fact, we handled a comparable setup while automating compliance data syncs in our AI-Powered ESG Platform, ensuring safe API writes and complete audit trails — the same discipline applies here.
:page_facing_up: Case Study

I can review your existing Make scenario, finalize headers, and test /search and /upsert payloads to ensure full data integrity before deployment.
Would you like to share your current Make setup screenshots or UAPI doc so I can map the safest logic for customer creation?

Best,

:date: Schedule a quick chat

8

Hi @3PDan,

Looks like you’ve already mapped out most of the logic — great groundwork. The missing piece sounds like header authentication + router safeguards to ensure the /search and /upsert calls never overwrite existing customer data.

I’ve handled similar REST API integrations (including Acuity, Commerce7, and WineDirect) using Make.com with Base64 + Bearer hybrid headers, dynamic filters, and safe upsert structures.

Happy to review your partial scenario and documentation to finalize the HTTP configuration and build-in overwrite protection.
You can also connect securely via Fiverr workspace or book a quick call to go over it live:

Best,
Mavin C
Automation & API Integration Expert

9

Hi Dan,

I specialize in Make.com integrations involving API authentication, router logic, and safe data handling. I can finalize your Acuity–OrderPort setup, ensuring clean conditional flows and full protection against data overwrites.

:page_facing_up: Check my profile: https://www.upwork.com/freelancers/farhana401

:telephone_receiver: Book a quick call:https://calendly.com/automaxion-meet

I’m ready to start immediately happy to review your scenario and UAPI documentation to provide a precise estimate.

10

Thanks everyone for the interest in helping with this project, here is the attached UAPI Doc for orderport api if anyone can confirm this can be accomplished

UAPI.pdf (917.5 KB)

11

Hi Dan,

Yes — this integration is definitely achievable. The OrderPort API uses a simple Base64 Bearer key, not OAuth, so we can connect it safely through Make.com. I can help finalize your current setup — test the headers, handle the search/upsert logic, and make sure no data gets overwritten.

If you’re ready to move forward, we can jump on a quick callto review your scenario and confirm the flow securely through Fiverr chat before starting officially.

Let me know a good time for you.

Best,
Mavin C.

12

Hey Dan!

Your OrderPort integration is almost there - the tricky part is ensuring that search endpoint properly returns empty arrays (not errors) when emails don’t exist, and that your upsert logic has proper safeguards against overwrites.

Key areas we’ll address:

1. HTTP Search Module Configuration:

Headers:
{
  "Authorization": "Bearer {{base64_encoded_key}}",
  "Content-Type": "application/json",
  "Accept": "application/json"
}

2. Router Logic with Proper Filters:

  • Route 1: {{length(http.response.data)}} > 0 (customer exists)
  • Route 2: {{length(http.response.data)}} = 0 (create new)

3. Safe Upsert Implementation:

  • Add field-level validation before upsert
  • Implement “create-only” logic using POST instead of PUT
  • Map Marketing Opt-In with proper boolean conversion

What we’ll deliver:

  • Complete tested scenario with proper error handling
  • Documentation of all API calls and safety checks
  • Testing protocol to verify no data overwrites
  • Handoff guide for your team

We’ve built similar CRM integrations with Commerce7 and WineDirect - the pattern is identical to OrderPort’s UAPI structure.

I can start immediately and have this production-ready within 24 hours.

Let’s review your current setup and finalize this: Make Discovery Session | Flow Digital

Sam @ Flow Digital