Hi,
I want help creating scenarios to connect Cliniko and Active Campaigns with Make. If you have expertise in creating these please let me know. Thank you!
4 Likes
Hi Garima,
I can help with setting up Cliniko and ActiveCampaign scenarios in Make. I’ve built similar integrations (syncing contacts, appointments, and automations). Happy to jump on a quick call or outline the setup for you, let me know.
You can reach me at [email protected].
Hello @Garima_Bharti , 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
Hi @Garima_Bharti ! I would love to help you with your automation.
We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.
If you are interested we would love to help you, you can schedule a call in here: https://cal.com/aspirity/discovery?utm_source=make discovery or check our website www.aspirity.com
Hi Garima, welcome to the community.
This is a common and solid use case. I’ve worked on similar setups connecting tools like Cliniko with ActiveCampaign for syncing contacts, appointments, and triggering follow up automations.
Typically this would involve capturing patient or booking data from Cliniko and pushing it into ActiveCampaign to manage sequences and engagement.
Quick question, what actions do you want to trigger in ActiveCampaign, is it mainly contact sync, automations, or both?
You can check out some related automation setups I built here in my portfolio website.
Feel free to DM me, happy to help you structure this properly.
Best regards,
Folafoluwa Stephen
I can definitely help you with that. I specialize in building Make.com integrations, and I’ve worked with both Cliniko (handling patient data/appointments) and ActiveCampaign (managing customer journeys).
How I usually structure this integration:
-
Data Flow: Syncing new patients or appointment status changes from Cliniko to ActiveCampaign tags.
-
Automation: Triggering personalized email/SMS sequences based on patient activities (e.g., “Post-visit check-in” or “Appointment reminder”).
-
Data Cleaning: Ensuring that patient data is properly formatted before it hits ActiveCampaign to avoid duplicate contacts.
-
Error Handling: Making sure that if an API call fails, the record is flagged so you never lose patient contact info.
I can build these scenarios as modular templates that you can easily maintain.
Portfolio: https://mikedevai.netlify.app/ Telegram: @hely_chatbots WhatsApp: +375293761570
Hi Mike. Thank you for your message. Can you please give me a quote please? I need to set up 4 or 5 scenarios in make to connect with my automations in Active campaigns which I have already set up
This post was flagged by the community and is temporarily hidden.
Garima, I would start by defining exactly which Cliniko event should trigger ActiveCampaign and which fields are safe to send. For healthcare/booking workflows, the safest setup is usually to keep the ActiveCampaign payload minimal and avoid sending patient notes or sensitive clinical details unless your compliance setup explicitly allows it.
A clean first milestone would be: one Cliniko appointment or contact event, a Make filter that separates create/update/cancel actions, one normalized contact payload, and one ActiveCampaign tag or automation trigger with duplicate protection. After that, reminders or follow-up sequences can be added without guessing at the data model.
TinyOps Studio can do a fixed $149 audit and return the scenario map, field list, and privacy-safe handoff checks. If useful, email [email protected] with the Cliniko event you want to trigger from and the ActiveCampaign automation you want to start.
Hi Garima. I can help connect Cliniko and ActiveCampaign through Make. I would start with one safe workflow: define the trigger, map only the needed fields, test with dummy data first, add failure notifications, and document the scenario. Before touching real client data, I would confirm what data is allowed to move between systems.