How to Use Make.com with iMessage: Automation Setup Guide

Make.com (formerly Integromat) and iMessage work together through Tuco AI's REST API. If you're already building automations in Make, adding iMessage as an output channel takes about 20 minutes. Below is the exact setup for the three most common use cases.

Why Use Make.com Instead of Zapier for iMessage?

Both work. But Make has advantages for teams that need more than simple A-to-B automations:

• Visual scenario builder. See your entire workflow as a flowchart, not a linear list.
• Branching and routing. Send different messages based on lead source, location, or any data field.
• Error handling built in. Retry failed API calls automatically, route errors to alerts.
• Better pricing for volume. Make's free plan includes 1,000 operations/month vs Zapier's 100 tasks.
• Data transformation. Format phone numbers, clean names, merge fields without separate steps.

If you're running simple "new lead → send message" workflows, Zapier works fine too. For anything with conditional logic, Make is more flexible.

How Does the Make.com + Tuco AI Connection Work?

The flow:

1. Trigger module fires (new lead, form submission, webhook, schedule)
2. Make processes data. Maps fields, applies filters, formats variables.
3. HTTP module sends POST request to Tuco AI's API
4. Tuco AI delivers iMessage through Apple's infrastructure
5. Webhook module (optional) receives replies from Tuco AI

All visual. Drag modules, draw connections, map fields. No code unless you want it.

Use Case 1: Facebook Lead Ads to iMessage

This is the highest-ROI automation for local businesses and agencies. A lead fills out your FB form. An iMessage hits their phone before they close the browser.

Setup Steps

Module 1: Facebook Lead Ads trigger

1. Add the Facebook Lead Ads module as your trigger
2. Connect your Facebook account
3. Select your Page and Lead Form
4. Test to pull in a sample lead

Module 2: HTTP — Make a Request

1. Add an HTTP module after the trigger
2. Configure:
   • URL: Your Tuco AI API endpoint
   • Method: POST
   • Headers:
     • Authorization: Bearer [your-api-key]
     • Content-Type: application/json
   • Body type: Raw
   • Content type: JSON
   • Request content:

{
  "to": "{{1.phone_number}}",
  "from": "your-tuco-number",
  "message": "Hey {{1.first_name}}, saw you were interested in {{1.form_name}}. Quick question: what's your biggest priority right now?"
}

3. Test the module. Verify iMessage arrives on a test number.

Module 3 (optional): Router for SMS fallback notification

Add a Router after the HTTP module. If the API response indicates SMS fallback (non-iPhone user), route to a Slack notification so your team knows to follow up differently.

Expected Results

Based on campaigns we've run for home services and lawn care clients:

• Speed-to-lead: iMessage arrives 5-15 seconds after form submission
• Response rate: 15-25% within the first hour
• Booking rate: 8-12% of respondents schedule an appointment

Compare that to SMS follow-up (3-5% response) or email follow-up (1-2% response on cold leads).

Use Case 2: Form Submission to iMessage

Works with Typeform, JotForm, Gravity Forms, or any form tool that supports webhooks.

Setup Steps

Module 1: Webhooks — Custom Webhook

1. Add a Webhooks module (instant trigger)
2. Copy the webhook URL Make generates
3. Paste that URL into your form tool's webhook settings
4. Submit a test form to register the data structure

Module 2: HTTP — Make a Request

1. Same configuration as the FB Lead Ads example
2. Map phone number and name fields from the webhook payload
3. Write your message template

Message template for form submissions:

Hi [first_name], got your request about [service_type]. We usually get back to people within the hour. Is now a good time for a quick call, or would tomorrow work better?

Asking for a preferred time gives the lead an easy way to respond and moves the conversation toward booking.

Use Case 3: CRM Event to iMessage

Trigger iMessages based on pipeline changes, deal stages, or contact properties in your CRM.

HubSpot Example

Module 1: HubSpot — Watch Deals

1. Set trigger to fire when a deal moves to a specific pipeline stage (e.g., "Demo Scheduled")
2. Pull contact phone number and name from the associated contact

Module 2: HTTP — Make a Request

1. POST to Tuco AI API with the contact's details
2. Message example:

Hey [first_name], looking forward to our call on [deal_date]. Quick heads up: I'll be sharing a 5-minute walkthrough of [product_feature]. Any specific questions you want me to cover?

This pre-demo message increases show rates. From our data: teams that send iMessage confirmations see 23-53% higher show rates than email-only confirmation.

Salesforce Example

For Salesforce-specific setup: How to send iMessage using Salesforce.

How Do You Handle Inbound Replies?

Tuco AI sends replies back through webhooks. In Make.com:

1. Create a separate scenario for inbound messages
2. Add a Webhooks module as the trigger
3. Configure your Tuco AI account to send reply webhooks to this URL
4. Add modules to process the reply:
   • Router to branch based on reply content ("yes" vs "no" vs other)
   • HubSpot/Salesforce to log the reply as an activity
   • Slack to notify the assigned rep
   • HTTP to send an automated follow-up based on the reply

What Does This Cost?

Make.com's free plan (1,000 operations/month) handles roughly 30 automations per day. For most teams, that covers the first few months. The Core plan at $9/month bumps you to 10,000 operations.

Make.com is $10/month cheaper than Zapier for equivalent functionality, and the free tier is more generous.

Common Setup Mistakes

Not formatting phone numbers. Make sure phone numbers include country code (+1 for US). Add a Set Variable module to prepend +1 if your form captures 10-digit numbers.

Missing error handling. Add an Error Handler module after your HTTP request. If the API returns an error (invalid number, rate limit hit), route to a Google Sheet or Slack channel for manual review.

Sending outside business hours. Use Make's Schedule settings to run scenarios only during business hours. Or add a Tools: Set Variable module that checks the current time and routes to a delay if it's after hours.

Getting Started

1. Sign up for Tuco AI and get API credentials
2. Create a Make.com account (free tier works for testing)
3. Build your first scenario using one of the use cases above
4. Test with your own phone number
5. Go live with a small lead segment

For other integration options: iMessage + Zapier | iMessage + Clay

View Tuco AI pricing | Book a demo

Related reading:

• iMessage + Zapier integration guide
• iMessage + Clay for signal-based outbound
• How iMessage increased demo show rates from 23% to 53%
• How to use iMessage with HubSpot sequences