I’m looking for an experienced Make.com specialist to build a complete AI-powered SMS automation system. The project involves 6 scenarios and approximately 41 modules.
What it does: Receives inbound SMS and MMS messages, passes them to an AI language model, fires two simultaneous API calls to external data sources in parallel, collates the results, and sends a formatted SMS reply back to the user.
Tech stack — all accounts active and ready:
Sinch (SMS) · Claude Haiku (AI) · Rainforest API · SerpApi · Carrd webhook
Key technical requirements:
∙ Parallel API calls firing simultaneously in Scenario 2
∙ MMS photo handling — download, base64 encode, pass to AI
∙ Phone number normalization to E.164 format
∙ Concurrent search protection with per-user processing lock
∙ Re-engagement automation sequences
∙ 5 data stores for users, analytics, savings, and redirect tracking
All credentials ready. An NDA will be signed prior to the full development scope document being handed over.
Payment: Fixed price · PayPal only · 30/30/40 split with video call milestone demo required.
Reply here or email contact@snipeagent.ai with your experience and examples of previous Make.com builds.
Hey, this is right up my alley, I’ve built complex Make.com systems with parallel API calls, AI processing, SMS workflows, and data store architectures. Your setup (Sinch + Claude + APIs + locking logic) is very familiar.
Happy to take this on and deliver clean, scalable scenarios with proper error handling and concurrency control.
Hello @Alex_T1 , 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
Your setup sounds like a solid architecture. I’ve worked on complex Make automation systems involving parallel API calls, AI processing, webhook triggers, and SMS workflows.
Handling inbound SMS/MMS, passing the data through an AI model like Claude, triggering multiple external APIs in parallel, and formatting responses back to the user is definitely achievable with a well structured Make scenario setup.
I also have experience building workflows with data stores, concurrency control, and API based integrations, so I’d be happy to review the scope once the NDA is in place.
You can check out some of my previous automation work here in my website portfolio .
I’ve reviewed your technical requirements for the SMS automation system. Building a multi-scenario architecture with parallel API execution and per-user locking is exactly the kind of “bulletproof” logic I specialize in.
How I will handle your specific technical needs:
Parallel Execution: I’ll implement the simultaneous API calls to Rainforest and SerpApi using Make’s HTTP Request modules in parallel routes, ensuring results are collated efficiently before the AI processes the final response.
MMS & Image Processing: I have extensive experience with binary data handling—downloading media from Sinch, encoding to Base64, and passing it to Claude Haiku for vision-based analysis.
Concurrency & Data Integrity: To handle the “per-user processing lock,” I will utilize Data Stores to manage state flags, preventing overlapping executions for the same phone number.
Data Architecture: I’ll set up the 5 required data stores with clean indexing for analytics, user tracking, and E.164 normalization logic to ensure global SMS compatibility.
Re-engagement: I’ll build the automated sequences to trigger based on inactivity or specific user segments stored in your analytics DB.
Why me?
Systems Architect: I don’t just “drag and drop.” I build systems with error handling and stable data flows.
Tech Stack Match: I’m highly proficient with Claude/OpenAI API, Webhooks, and complex Data Store logic.
Portfolio: My own website and professional builds involve complex n8n/Make architectures and automated booking systems. You can see my work here: https://mikedevai.netlify.app/
Terms & Next Steps:
Payment: I’m fully onboard with the 30/30/40 split via PayPal and the video call milestone demos.
NDA: Ready to sign the NDA to begin the full scope review.
The SMS automation architecture you’ve described — Claude Haiku for real-time AI processing, parallel API calls (Rainforest, SerpApi), MMS handling with base64 encoding, concurrency locks, and re-engagement sequences — this is exactly the kind of complex multi-step workflow I specialize in.
Relevant experience:
Claude API in Make.com/n8n: Production workflows using Haiku for fast classification and Sonnet for deeper analysis. Structured JSON output handling with retry logic. Details and case studies: priyanshukumar.co
API orchestration: Built systems integrating 7+ APIs with pagination, rate limiting, and error recovery.
Data stores and state management: Designed multi-table architectures for tracking conversation state, deduplication, and sequential processing.
Comfortable with the fixed-price milestone structure (30/30/40) and video call demos for each phase. Also fine with NDA before receiving the full scope doc.
