Overview:
We’re looking for an experienced Make.com specialist to build and maintain automations across our tech stack. We have several builds ready now, with ongoing work expected.
Scope:
Build automations in our Make.com instance (all work must live in our environment)
Integrate Slack, ClickUp, Google Workspace, and Claude (API-based workflows)
Turn defined ideas into reliable, scalable automations
Set up monitoring systems and error alerts
Document builds for ongoing maintenance
What We’re Looking For:
Strong, proven experience specifically in Make.com
Experience with APIs, webhooks, and multi-step workflows
Ability to troubleshoot, optimize, and maintain automations
References or examples of past work
Details:
~10 hours/week or project-based (flexible)
Ongoing opportunity as new automations are created
Expectation to monitor builds and ensure performance over time
To Apply:
Share examples of Make.com automations you’ve built, relevant integrations, and references.
Hey @Lindsey_Moore , I’ve built and maintained Make.com automation systems across Slack, ClickUp, Google Workspace, and AI APIs including Claude, with a strong focus on reliability, error handling, and long-term maintainability. I can work directly inside your Make environment, turn defined workflow ideas into production-ready scenarios, and set up proper monitoring, alerting, and documentation so builds are easy to manage over time. My approach is to standardize modules, reduce failure points, handle edge cases up front, and make each automation scalable as volume grows. I’m also comfortable troubleshooting existing scenarios, optimizing API usage, and improving performance where current builds are fragile or inefficient. If helpful, I can share relevant examples of multi-step Make workflows and integration patterns I’ve implemented. Send over the first automation scope or access details, and I can review and start immediately. You can book a call with me here to discuss this further. View some of my make.com workflows here .
hey — we run an AI ops service (getheadcount.io) where our agent Kai builds and maintains automations across SaaS stacks like Slack, ClickUp, Google Workspace, and Claude API workflows.
instead of someone manually building in the GUI 10 hrs/week, we work with Make.com’s API to programmatically create, deploy, and monitor scenarios. faster to ship, easier to maintain, proper error handling baked in.
don’t have Make.com-specific examples to share yet, but here’s what i’ll offer — pick one of your builds, let us do it. if it works well, we figure out pricing from there. no risk on your end.
happy to jump on a quick call if you’re open to it.
Hi Lindsey,
You can leave me a message here or put some time in to my calendar here.
Also see website Genesys Automation.
I am a expert Make.com developer. I have built and model processes for fast and reliable functionalities.
While I am tool/CRM agnostic, I have built ClickUp automation systems like:
Have sent you a DM as well. Would love to help you with the Make automations. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency. I am Make advanced certified, Clickup certified expert 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 LearnWorlds with Airtable, Make, and Pipedrive via API handling complex pagination and syncing data in real time.
• For a fintech startup in Amsterdam (raised €8.1M), I automated lead flows and built a custom Slack bot designed to alert team members about merchants at risk of churn.
• For a bakery brand with a large social following, I implemented chatbots integrated with a custom CRM in Airtable and automation workflows to handle orders and FAQs saving hours of manual coordination every day.
Would love to learn about your current Make workflows and your day to day operations
I’m a Make.com automation specialist and have built and maintained multi-step workflows integrating Slack, ClickUp, Google Workspace, and AI APIs like Claude. Most of my work focuses on building reliable automation systems with proper error handling, monitoring, and scalable architecture.
I’ve implemented workflows for operations automation, AI pipelines, data synchronization, and multi-tool integrations using webhooks and APIs.
You can see examples of my past automation works here my portfolio website.
If helpful, I’d be happy to take a look at one of your existing automations and suggest improvements or help implement new workflows.
Hello @Lindsey_Moore , 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
I’ve reviewed your scope, and it aligns perfectly with my engineering approach. I don’t just “connect apps”; I build reliable, documented, and fault-tolerant systems that can be easily maintained within your Make.com environment.
How I will support your tech stack:
Deep Integrations: I have extensive experience orchestrating ClickUp, Slack, and Google Workspace. I specialize in complex state management (e.g., syncing task statuses in ClickUp with real-time Slack notifications and automated document generation in Drive).
AI-Powered Workflows: I’m highly proficient in Claude/OpenAI API integrations—moving beyond simple prompts to building agentic workflows that actually process data and deliver structured results.
Infrastructure & Stability: I implement professional Error Handling (Break/Resume logic) and Monitoring Systems. Every build I deliver includes an automated alert system (via Slack/Email) so you’re the first to know if an API hangs or data is missing.
Documentation: I provide clear mapping of scenarios and logic, ensuring your team has full transparency into how the “digital workers” operate.
Why me?
Technical Depth: With a background in JavaScript and SQL, I can write custom functions when Make’s native modules hit a wall.
Ownership: I’m looking for a long-term partnership where I can monitor performance and optimize workflows as your business evolves.
Hi @Lindsey_Moore, I’m an AI Automation Engineer and I specialize in exactly the stack you mentioned (Make + Claude + ClickUp).I focus on ‘Defensive Automation’—meaning I don’t just build the workflow; I build the monitoring and error-alert systems you mentioned to ensure 100% uptime. I recently engineered a HITL system that uses Claude for high-fidelity data parsing with a Slack approval UI.Technical Walkthrough:Preventing AI Hallucination in Code Outreach with Human-in-Loop Workflow ✉️ | Loom I am available for 10 hours/week and would love to audit your current instance to see where we can optimize your Claude API calls to save on tokens. Are you open to a brief chat next week?
This looks like a good fit — I build and maintain automation systems across exactly this stack.
Relevant experience:
Claude API integration in automation workflows — I use Claude daily for structured extraction, classification, and multi-step reasoning inside automated pipelines. Both Haiku (fast processing) and Sonnet (complex analysis). Recent work: priyanshukumar.co
Slack + ClickUp + Google Workspace — built notification systems, task creation flows, and reporting dashboards that connect these tools via API.
Monitoring and error handling — every system I build has retry logic, failure notifications, and structured logging. Nothing fails silently.
Documentation — I document every workflow with clear explanations of what it does, why it’s built that way, and how to maintain it.
I typically work async-first and am comfortable with ~10 hours/week ongoing. Happy to start with one of the builds you have ready and go from there.
We’re excited to submit our proposal for the Make.com Automation Specialist role. At Effinyx Technologies, we specialize in designing and deploying scalable automation systems that streamline operations, reduce manual overhead, and improve data flow across complex tech stacks.
Why We’re a Strong Fit
We bring hands-on expertise in Make.com (Integromat) with a strong focus on building production-grade automations. Our team has extensive experience working with:
Multi-step workflows involving APIs, webhooks, and conditional logic
Integration of tools like Slack, ClickUp, Google Workspace, and AI platforms such as Claude
Designing resilient systems with retry mechanisms, logging, and fallback strategies
Structuring automations for scalability and long-term maintainability
Relevant Experience
Built end-to-end automation systems syncing CRM, internal tools, and databases using Make.com
Designed webhook-based pipelines for real-time data processing and notifications
Implemented AI-powered workflows (Claude/OpenAI) for content generation, classification, and decision-making
Created monitoring layers with error handling, alerting (Slack/Email), and execution tracking
Delivered well-documented automation systems for seamless handover and scaling
How We Work
All automations will be built directly inside your Make.com environment
We follow a modular approach to ensure clarity, flexibility, and ease of debugging
We understand that automation isn’t “set and forget.” We offer:
Continuous monitoring and optimization
Rapid debugging and issue resolution
Iterative improvements as your workflows evolve
Availability
Flexible engagement (~10 hours/week or project-based)
Ready to start immediately
Long-term collaboration aligned with your roadmap
Closing
We’re confident in our ability to turn your defined ideas into robust, scalable, and intelligent automation systems. We’d be happy to share specific case studies or walk through similar builds we’ve delivered.
Looking forward to collaborating.
Best regards, Effinyx Technologies
Automation & AI Solutions Team
I can help you build automations on your make.com account to Integrate Slack, ClickUp, Google Workspace, and Claude, and maintain the scenarios. We can talk more on a call
Hi Lindsey, this is close to the kind of Make/API work I’m looking for.
My strongest fit is where the workflow needs to be supportable long-term: webhooks, API calls, structured routing, Claude outputs, error alerts, documentation, and clean handoff inside the client’s own Make environment.
For your stack, I’d normally approach it this way:
define the source of truth for each workflow
keep AI outputs human-reviewed where needed
add failure alerts before launch
document the trigger, key mappings, tools touched, and recovery steps
keep scenarios readable enough that your team is not dependent on a black box
Relevant proof I can share: a Make bridge walkthrough showing Laravel => Make webhook => routing => Sheets/Gmail/error paths, plus a reliability walkthrough showing queues, webhook logs, retries, failed jobs, and operator visibility.
A few questions:
Are the current builds mostly new workflows or maintenance of existing scenarios?
Who handles QA/signoff after each workflow?
What does monitoring mean for you: Make alerts, Slack alerts, external logs, or all of the above?
Is the first month closer to 10 hours/week, or is there a larger backlog?
A practical way to start is one paid Make build from your backlog, then expand only after you see the run quality.
I can take one workflow involving Slack, ClickUp, Google Workspace, or Claude API, build it in your Make workspace, add error alerts/run notes, and leave the next maintenance steps clear for your team.
TinyOps Studio can do the first workflow for a fixed $499. Send the first automation brief and one expected input/output example, and I can confirm the scope.
This is close to the kind of Make/API work West Work Studio handles.
The part that stood out is the ongoing maintenance piece. For Slack, ClickUp, Google Workspace, and Claude workflows, I would focus less on clever scenarios and more on making the system supportable: clean module naming, error alerts, run notes, and documentation your team can use after each build.
A few questions:
Are the first builds mostly new workflows or cleanup of existing ones?
Do you want alerts inside Slack, Make, or both?
Who signs off when a workflow is ready to go live?
If helpful, I can look at one workflow brief and suggest the first build path.
Hi Lindsey. I can help with Make scenarios that need API/webhook reliability, monitoring, and clean handoff docs. I would start with one small paid slice: take one defined automation, add missing error paths and alerts, verify it with test data, and document how your team maintains it. Which build is the highest priority right now?
!!!