Skip to main content

~20 minutes setup

What You'll Need

Prerequisites before starting

Common Use Cases

Start here, find your own use case

Quick Path

Condensed steps for experienced users

Step-by-Step Setup

Complete walkthrough (Steps 1–6)

Advanced Automations

Filters, routers & real-world examples

Quick Checklist

Verify your setup is complete

Troubleshooting & FAQs

Common issues & fixes

Introduction

You’ve built your conversational AI agent on Irelia.ai, and it’s actively chatting with prospects on WhatsApp, Facebook, and Instagram. But what happens when something important occurs — like when a lead gets qualified, when your agent collects key information, or when someone books a meeting? Right now, you might be manually checking your Irelia dashboard and copying information to other tools. There’s a better way. Irelia tracks these important milestones as events — the “moments that matter” in your conversations. This guide shows you how to automatically send event data from Irelia to your other business tools the instant it happens — no manual work, no delays, no checking dashboards. By the end of this guide, you’ll have: ✅ A working automation that triggers when specific events happen in your Irelia conversations
✅ Data flowing automatically from Irelia to your CRM, spreadsheets, or team chat
✅ The knowledge to build unlimited additional automations

How This Works

Think of this connection like a smart doorbell system: The magic: Everything happens automatically in seconds. No manual work. No delays. No checking dashboards.

What You’ll Do

  1. 🔗 Get a webhook URL from Make.com — 3 min
  2. 📋 Paste the URL into Irelia — 2 min
  3. 🧪 Send test data — 2 min
  4. ⚡ Set up your action (Google Sheets, Slack, etc.) — 5 min
  5. ✅ Test everything end-to-end — 3 min
  6. 🚀 Turn it on and name it — 1 min
Total: ~15–20 minutes

📋 What You’ll Need

  • An Irelia.ai account with at least one active agent Required
  • A Make.com account (free tier works fine) — Sign up here if needed Required
  • A destination for your data (Google Sheets, Slack, or your CRM) Required
No coding required. If you can copy and paste, you can do this.

🎯 Common Use Cases

80% of readers need one of these two setups. Find yours, note the guidance, then follow the Step-by-Step Setup below — you’ll just make different selections at Step 2 and Step 4.
Update my CRM or spreadsheet when a lead qualifies or a goal is completedExamples: lead marked as qualified → update HubSpot status · meeting booked → log it in your sheet · goal completed → notify your sales team📡 Select this event in Step 2: Lead Qualified or Goal AchievedWhich steps do I follow?
  • Contact already exists in your CRM or spreadsheet → follow Steps 1–3, then use the Search and Update Existing Records pattern for Step 4.
  • Contact is brand new (not yet in your system) → follow Steps 1–6 as written (Example A, B, or C in Step 4).
Most common mistake: The contact likely already exists in your system (you probably added them on first contact). If you use “Add a Row” or “Create a Contact” again, you’ll get duplicates. Use the Search and Update Existing Records pattern for Step 4 instead.

📡 Available Events Reference

Your AI agent tracks several types of events as it chats with prospects. Below are some examples of events Irelia can notify you about: When an event triggers, Irelia packages all the relevant information — prospect details, conversation history, qualification status, custom data — and sends it to Make.com instantly.
Don’t see your use case? No problem — follow the guide using “New Inbound Contact” as your learning event. The process is identical for every event; only your selections at Step 2 and Step 4 change.

⚡ Quick Path (Experienced Users)

Already comfortable with Make.com? Here’s the condensed version:
  1. Make.com: Create Scenario → Add Module: “Webhooks” → Select “Custom webhook” → Create webhook → Copy URL
  2. Irelia: Settings → Select Agent → Events and Notifications → Paste URL into desired event field
  3. Test: Click “Test” button in Irelia → Return to Make.com → Verify data structure determined
  4. Action: Add your action Module → Map fields → Run once → Activate
Need more detail? Continue with the full guide below.

🔧 Step-by-Step Setup

Step 1: Set Up Make.com to Receive Irelia Notifications

~3 minutes In this step, you’ll create a new and configure it to listen for events from Irelia. For this guide, we’ll use “New Inbound Contact” because it’s easy to trigger and perfect for learning. Once you understand how it works, you can easily set up other events.

Create your Scenario

  1. Log into your Make.com account at make.com
  2. Click the “Create a new scenario” button (or the + icon in the top right)
Irelia.ai Make.com integration guide, Step 1 - Set Up Make.com to Receive Irelia Notifications, Create your Scenario. Shows the Make.com organization dashboard with usage charts and credit stats, with the Create scenario button highlighted top right. This is where the reader starts building the new automation that will receive Irelia webhook events.

Click 'Create a new scenario' to start building your automation

  1. You’ll see the Scenario editor — a visual canvas where you’ll build your automation
    • You’ll start with an empty canvas showing a large + icon in the center

Add the webhook Module

  1. Click the + icon in the center of the canvas
  2. A search box will appear — type webhooks
  3. Select “Webhooks” from the results
Irelia.ai Make.com integration guide, Step 1 - Add the webhook Module. Shows the Scenario editor's app search panel with the search term webhooks typed in, and the Webhooks (Built-in) app highlighted at the top of the results list next to the empty plus-icon canvas. This is where the reader selects the Webhooks app to start building the trigger for the automation.

Search for 'webhooks' and select the Webhooks Module

  1. From the list of triggers, select “Custom webhook”
Irelia.ai Make.com integration guide, Step 1 - Add the webhook Module. Shows the Webhooks app panel with its Triggers and Actions lists, where the Custom webhook trigger, marked Instant, is highlighted below Custom mailhook and above the Webhook response action. This confirms the correct trigger type to pick so the Scenario can listen for data sent by Irelia.

Select 'Custom webhook' as the trigger type

Create your webhook and get the URL

  1. A configuration panel will open. Click “Add” to create a new webhook
Irelia.ai Make.com integration guide, Step 1 - Create your webhook and get the URL. Shows the Webhooks configuration panel with an empty Choose a hook dropdown and the Add button highlighted on the right, which opens the dialog to create a brand-new webhook. This is the action that generates the unique Make.com endpoint Irelia will later send event data to.

Click 'Add' to create a new webhook endpoint

  1. Give your webhook a descriptive name (e.g., “Irelia - New Inbound Contact”)
  2. Leave all other settings at their defaults
  3. Click “Save”
Irelia.ai Make.com integration guide, Step 1 - Create your webhook and get the URL. Shows the Create a webhook dialog with the Webhook name field filled in as Irelia - New Inbound Contact, highlighted at the top, and the Save button highlighted at the bottom right next to Close, above the API Key authentication options. Naming the webhook clearly here makes it easy to recognize later inside Make.com.

Name your webhook and click Save to generate the URL

  1. Make.com will generate a unique webhook URL
    • It looks like: https://hook.make.com/abc123xyz789...
  2. Click the “Copy address to clipboard” button
Treat this URL like a password. Anyone with your webhook URL can send data to your Make.com account. Don’t share it publicly or include it in screenshots you post online.
Keep this Make.com tab open exactly as you see it in the image below! You’ll need to return here in a few minutes.
Irelia.ai Make.com integration guide, Step 1 - Create your webhook and get the URL. Shows the Webhooks panel with the generated address starting with hook.eu2.make.com displayed in full, the red Stop button, and the Copy address to clipboard button highlighted on the right while Make.com waits for incoming data. The reader copies this address here and keeps the tab open to paste it into Irelia next.

Keep this tab open — you'll return here after configuring Irelia

Step 2: Tell Irelia Where to Send Notifications

~2 minutes Now you’ll log into Irelia and paste the webhook URL you just copied. In Irelia, each AI agent can have its own automations. For this guide, you’ll configure ONE event for ONE agent. Once you understand how it works, you can easily set up more.

Access your agent settings

  1. Log into your Irelia.ai settings dashboard
  2. Select the agent you want to connect to Make.com
Irelia.ai Make.com integration guide, Step 2 - Access your agent settings. Shows the Irelia Agents list for the NextWave AI organization with three agent cards, Nuovo Agente, Agente creato da Wizard 1, and Agente creato da Wizard, with the middle card highlighted by a red box and arrow. Selecting the right agent here determines which conversational agent gets connected to the Make.com Scenario.

Select the agent you want to connect to Make.com

  1. Navigate to “Events and Notifications”
Irelia.ai Make.com integration guide, Step 2 - Navigate to Events and Notifications. Shows the agent settings page with the tabs Trigger, Prompt, Follow-up, and Events and notifications, the last tab highlighted in red at the top, above the Email address to notify field and the Events, integrations and notifications section. Opening this tab is where all webhook fields for the agent's events live.

Open the Events and Notifications section

Configure your webhook

  1. You’ll see a list of available events
Irelia.ai Make.com integration guide, Step 2 - Configure your webhook. Shows the Events, integrations and notifications section listing three event rows, New inbound contact reaching out to us, New contact for outbound outreach, and New information gathered, each with its own empty URL field and blue Test button, with red arrows pointing at all three webhook icons. This is the full list of events the reader can choose to connect to Make.com.

Available event types with URL fields for webhook configuration

  1. Find “New inbound contact reaching out to us” (or the event you wish to configure)
Picking the right event? If you’re following a specific use case from above, select the event listed there instead of “New Inbound Contact.”
  1. Click in the “URL” field next to this event
  2. Paste the webhook URL you copied from Make.com (the URL will auto-save)
Irelia.ai Make.com integration guide, Step 2 - Configure your webhook. Shows the New inbound contact reaching out to us event row with the copied Make.com webhook address, starting with hook.eu2.make.com, now pasted into the URL field, and the blue Test button highlighted with a red box. Pasting the URL here links this specific Irelia event to the Make.com Scenario created earlier.

Paste the Make.com webhook URL into the event URL field

Need to change the URL later? If you ever need a new webhook URL (changed Scenarios, troubleshooting, etc.), simply get a new URL from Make.com and paste it into Irelia. The old URL will stop working, and the new one will take over immediately.
Connected! This event will now send data to Make.com whenever someone first contacts this agent.

Step 3: Test the Connection

~2 minutes Now let’s verify that Irelia and Make.com can talk to each other.

Send test data from Irelia

  1. In your Irelia webhook configuration (where you just pasted the URL), find the blue “Test” button next to the webhook URL field
  2. Click “Test”
  3. You should see a green success indicator in Irelia that says “Just sent a data sample successfully”
Irelia.ai Make.com integration guide, Step 3 - Send test data from Irelia. Shows the same New inbound contact reaching out to us event row with the Test button, and a green confirmation banner at the bottom reading Just sent a data sample successfully, pointed out by a red arrow. This banner is the first proof that Irelia can reach the Make.com webhook.

Green success confirmation after sending test data

What just happened: Irelia sent sample data to Make.com. This sample data shows you exactly what kind of information Irelia will send when this event actually happens in a real conversation.

Verify Make.com received the data

  1. Go back to your Make.com tab (the one you kept open)
  2. You should see a success message: “Successfully determined” with a green checkmark
Irelia.ai Make.com integration guide, Step 3 - Verify Make.com received the data. Shows the Make.com Webhooks configuration panel with the webhook address field and a green status message reading Succesfuly determined, as it is actually spelled in the Make.com interface, highlighted with a red box next to the Copy address to clipboard button. This confirms Make.com has analyzed the sample data structure sent from Irelia.

'Successfully determined' confirms Make.com received the data

  1. Click “OK” to close the configuration panel
What “Successfully determined” means: Make.com has analyzed the data Irelia sent and now understands its structure. This allows you to use any of these data fields in your next steps.
Success! Irelia and Make.com are connected and talking to each other.

Understanding the Data Irelia Sends

Before setting up actions, take 60 seconds to understand what Irelia just sent to Make.com.
Irelia.ai Make.com integration guide, section Understanding the Data Irelia Sends. Shows the Make.com data-mapping panel listing every field from the Webhooks Custom webhook bundle, including the conversationFlow group (id, name, chatHistory, interestScore, leadQualification) and top-level fields like userName, userNumber, optStatus and customVariables. Reviewing this full field list helps the reader understand exactly what data is available before building any action.

All available data fields from the Irelia webhook

These data fields fall into three buckets: 1. 👤 Who They Are (Contact Info)
  • userName — The prospect’s name
  • userNumber — Their phone number
  • inboundLead — Did they message first (true) or did you (false)?
2. 💬 What Happened (Conversation Details) Per agent — the specific chat the user had with a specific agent (under the conversationFlow section):
  • id — Unique agent identifier
  • name — Name of the conversation agent
  • chatHistory — Complete conversation transcript with this agent
  • leadQualification — Are they qualified by this agent? ("fit", "not a fit", or "TBD")
  • interestScore — How interested are they? (0.0 to 1.0, like 0% to 100%)
  • reasonNotQualified — Why they didn’t qualify (if applicable)
  • goalAchieved — Number of goals completed with this agent
  • numberOfMessageSent — Messages sent by this agent
  • numberOfMessageReceived — Messages received from prospect
  • numberOfQuestionLackingData — Questions the AI couldn’t answer from Knowledge Base
  • creditConsumedForThisChat — Credits used for this conversation
Overall (across all agents):
  • chatHistory — Complete chat history across all agents
  • optStatus — Opt-in status (e.g., "in", "out")
  • creditConsumedForThisLead — Total credits consumed
  • numberOfMessageSent — Total messages sent
  • numberOfMessageReceived — Total messages received
  • numberOfQuestionLackingData — Total questions lacking answers
  • numberOfGoalAchieved — Total goals achieved
3. 📝 What You Learned (Custom Data)
  • customVariables — Specific information your agent collected (budget, company size, timeline, etc.)
Each custom variable has:
  • name — What you asked about (“Budget”)
  • value — Categorized answer (“$10k-50k”)
  • valueRaw — Exact words they used (“We have around 30k to spend”)
Irelia.ai Make.com integration guide, section Understanding the Data Irelia Sends. Shows the customVariables array expanded with sample entries such as Marca preferita, Budget, Nome and Email, each showing its name, value (Categorization Value Test) and valueRaw (Raw Value Test) fields, highlighted with a red box on the right side of the canvas. This shows exactly how each custom question the agent asks turns into three related data fields for mapping.

Expanded customVariables showing name, value, and valueRaw fields

Use these to: Fill CRM fields, personalize emails, segment leads, give sales reps context, route leads to different teams, and prioritize follow-ups.
Not all events send all data. The test you just ran shows you the data for “New Inbound Contact” events. Different events send different data. Don’t worry if you don’t see every field mentioned above — you’re seeing exactly what’s relevant for your event.

Step 4: Set Up Your Action

~5 minutes Now comes the fun part: deciding what should automatically happen when Irelia sends data to Make.com.

Choose your first action

Ask yourself: “When someone first contacts my agent, what’s the ONE most valuable thing that should happen automatically?” Common answers:
  • ✅ Log it immediately → Google Sheets (simplest, great for testing)
  • ✅ Alert my team → Slack (immediate visibility)
  • ✅ Add to my CRM → HubSpot, Salesforce, Pipedrive (most business value)
  • ✅ Start a sequence → Email marketing tool (begins nurture process)
Our recommendation for your first automation: Choose Google Sheets or Slack. They’re simple to set up, and you’ll immediately see when your automation works. Once you’ve tested the connection, you can always change the action to something more complex. Below you’ll find guided instructions for these two examples.
If you want to create more complex automations or connect different business tools, we suggest searching on YouTube for the exact outcome you wish to achieve (e.g., “How to add a row in Google Sheets using Make.com”).
Recommended for first-timers
  1. Hover over the right side of your webhook Module until you see a small + icon appear
  2. Click the + icon to add a new Module
Irelia.ai Make.com integration guide, Step 4, Google Sheets tab - hovering the webhook Module. Shows the Scenario canvas with only the Webhooks module placed, and a small plus icon labeled Add another module appearing on its right edge, pointed out by a red arrow. Clicking this plus icon is how the reader starts adding the action that will run after the webhook fires.

Click the + icon on the right side of the webhook Module

  1. In the search box, type Google Sheets
  2. Select “Google Sheets” from the results
Irelia.ai Make.com integration guide, Step 4, Google Sheets tab - select the app. Shows the app search panel with Webhooks listed under Apps in scenario, and Google Sheets, marked Verified, highlighted with a red box at the top of the All apps list next to Webhooks, Flow Control and Airtable. Choosing Google Sheets here sets up the destination for the automation's first action.

Select Google Sheets from the app list

  1. From the list of actions, select “Add a Row”
Irelia.ai Make.com integration guide, Step 4, Google Sheets tab - choose the action. Shows the Google Sheets module panel under the Rows section, with Add a Row highlighted in a red box above Update a Row, Bulk Add Rows (Advanced) and Bulk Update Rows (Advanced). Selecting Add a Row here is what will log every new lead as a fresh line in the spreadsheet.

Select 'Add a Row' to log lead data in your spreadsheet

  1. Click “Add” to connect your Google account (or select an existing connection)
  2. Follow the prompts to sign in and grant Make.com access to your Google Sheets
  3. Select your “Spreadsheet” from the dropdown (or create a new one first in Google Sheets)
  4. Select your “Sheet” (usually “Sheet1”)
Irelia.ai Make.com integration guide, Step 4, Google Sheets tab - select spreadsheet and sheet. Shows the Add a Row configuration panel with Connection set to My Google connection, Search Method Search by path, Drive My Drive, Spreadsheet ID Notifiche Irelia, and Sheet Name FREE TRIAL, all five fields marked with red arrows. Filling in these fields tells Make.com exactly which spreadsheet and tab will receive the new rows.

Select your target spreadsheet and sheet tab

  1. Map your fields — this is where you tell Make.com which Irelia data goes into which spreadsheet column
Make.com will show you all the columns in your spreadsheet. Click into each field, and a panel will appear showing all available data from Irelia. Simply click on the data you want to insert.
Irelia.ai Make.com integration guide, Step 4, Google Sheets tab - map your fields. Shows the Add a Row Values section with spreadsheet columns Email by time (A), (B) already mapped to the userName tag, and column (C) focused and empty, next to the Irelia data picker on the right listing userName, userNumber (highlighted, value 393123456789), userMessage, chathistory and other fields. This is where each spreadsheet column gets linked to the matching piece of Irelia data.

Map Irelia data fields to your spreadsheet columns

  1. Click “OK” to save the Module configuration
Skip to Step 5 →

Step 5: Test Your Complete Automation

~3 minutes Let’s test the entire workflow end-to-end to make sure everything works together.

Run your test

  1. At the bottom left of the canvas, click the “Run once” button
Irelia.ai Make.com integration guide, Step 5 - Run your test. Shows the completed Scenario canvas with three connected modules, Webhooks Custom webhook, Google Sheets Add a Row, and Slack Send a Message, and the Run once button highlighted with a red box at the bottom left. Clicking Run once here starts listening for the next test event to flow through the whole chain.

Click 'Run once' to execute the Scenario manually

  1. Make.com will start listening. You’ll see “Waiting for data…” on your webhook Module
  2. Go back to Irelia and click the “Test” button again to send fresh data
  3. Return to Make.com — you should see the data flow through both Modules
Irelia.ai Make.com integration guide, Step 5 - Run your test. Shows the same three-module Scenario, Webhooks, Google Sheets and Slack, each now displaying a small green checkmark badge with the number 1 above it, confirming every module processed the test data successfully. Seeing all three green badges together tells the reader the end-to-end automation worked.

Green checkmarks on both Modules confirm successful processing

  1. Each Module will show a number (like “1”) indicating how many items were processed
  2. Click on any Module to see the details of what was processed
Irelia.ai Make.com integration guide, Step 5 - Run your test, view execution details. Shows the Webhooks module execution panel open, with Summary 1 operation and 1 credit used, and the Operation 1 output bundle listing userName Test Name, userNumber 393123456789, userMessage Test Message, inboundLead true and other conversationFlow fields, highlighted with a red box and arrow. Opening this detail view lets the reader confirm exactly what data the webhook actually captured.

Expanded execution details showing the processed Irelia data

Verify it worked

Now check your destination to confirm:
  • Open your spreadsheet
  • Look for a new row at the bottom with the test data
  • You should see the prospect’s name, phone number, status, etc.
Irelia.ai Make.com integration guide, Step 5, Verify it worked - Google Sheets tab. Shows the Irelia.ai Google Sheets spreadsheet on the Foglio1 tab, with columns Nome e Cognome, Mail, Numero di telefono, Ref and Webinar, and a new row near the bottom containing Test Name and phone number 393123456789, pointed out by a red arrow. This new row is the proof that the Add a Row action actually wrote the test lead into the spreadsheet.

New row with test lead data added automatically

Did you see your data in the right place? Your automation works!

Step 6: Activate and Name Your Scenario

~1 minute

Activate your Scenario

  1. At the bottom left of your Scenario editor, find the toggle switch (it currently says “OFF”)
  2. Click the toggle to turn your Scenario ON
Irelia.ai Make.com integration guide, Step 6 - Activate your Scenario. Shows the three-module Scenario canvas with the bottom toolbar's Immediately as data arrives toggle, already switched on and purple, highlighted with a red box and arrow. Note: the surrounding text describes a separate OFF and ON Active switch, but this screenshot actually highlights the scheduling toggle rather than that Active control.

Toggle the Scenario from OFF to ON to activate it

  1. The toggle will turn blue/purple and display “ON”

Give your Scenario a name

  1. Click on the Scenario name at the top left (it probably says “New scenario” or similar)
  2. Rename it to something descriptive like: “Irelia: New Contact → Google Sheet”
Irelia.ai Make.com integration guide, Step 6 - Give your Scenario a name. Shows the top left of the Scenario editor with the name field renamed from New scenario to Irelia: New Contact to Google Sheet, highlighted with a red box and arrow. Renaming the Scenario here makes it easy to recognize among other automations later.

Rename your Scenario for easy identification

  1. Click the “Save” button (floppy disk icon) at the bottom of the screen to save your changes
Irelia.ai Make.com integration guide, Step 6, Give your Scenario a name - save it. Shows the same Scenario canvas with the save icon, a floppy disk symbol in the bottom toolbar, highlighted with a red box and arrow pointing down at it. Clicking this icon is what actually persists the rename and every other configuration change made so far.

Click the save icon to persist your Scenario configuration

Your automation is now live!

🎉 Congratulations! You Did It!

Take a moment to appreciate what you just built: ✅ Your AI agent now talks to your other tools automatically
✅ Important moments trigger instant actions
✅ No more manual data entry or checking dashboards — your systems are always up-to-date
✅ Your leads get faster, better follow-up
What happens now: Every time someone reaches out to your Irelia agent for the first time → Irelia automatically sends their information to Make.com → Make.com immediately performs your action → All without you lifting a finger.

What’s Next?

Now that you have one working automation, the possibilities are endless. If you want to connect to more events like “Data Gathered”, “Lead Qualified”, or “Goal Achieved”, simply repeat the steps and customize the actions (Step 4) to achieve your desired result. Your options from here:
  1. 🎯 Want to track another event? Create a new Scenario and repeat this guide — just select a different event in Step 2
  2. ➕ Want this Scenario to do more things? Edit your Scenario and click the + button after your last Module to add more actions
  3. 🤖 Have another agent to connect? Repeat this guide for your other agents — each can have its own automations
  4. ⚡ Ready for advanced workflows? Check out the Advanced Automations section below

Monitoring Your Automation

Check your Scenario history

  1. Open your Scenario
  2. Click on the “History” tab at the top of the editor
  3. Here you can see every time your Scenario runs:
    • ✅ Success (green indicators)
    • ❌ Error (red indicators with details)
Irelia.ai Make.com integration guide, section Monitoring Your Automation, Check your Scenario history. Shows the Irelia: New Contact to Google Sheet Scenario page with the Active toggle switched on top right, the Diagram, History and Incomplete executions tabs, and a History panel listing several runs marked with green Success badges along with operations, credits used and a data-transfer usage graph below. Checking this history regularly is how the reader confirms the automation keeps running correctly over time.

Scenario History showing successful runs with green indicators

  1. Click on any execution to see detailed information about what happened

What to monitor

First few days: Check daily to ensure Scenarios run successfully and data looks correct. Ongoing: Make.com can send you email notifications when Scenarios error out, so you don’t need to check constantly. Just verify things are working during the first few days.
Pro tip: Go to your Scenario settings (three dots menu → “Settings”) to configure error notifications and scheduling options.

🚀 Advanced Automations

Search and Update Existing Records

Sometimes you don’t want to create a new record — you want to update an existing one. For example, when a lead you already added gets qualified, or when new data is gathered for someone already in your system. This requires a two-step approach: search first, then update. Example: Update an existing lead’s row when they get qualified Trigger: Lead Qualified (webhook) Modules:
  1. Search for the existing row
    • Add Module: “Google Sheets” → “Search Rows”
    • Set “Search Column” to “Phone”
    • Set “Search Value” to userNumber from Irelia
    • This finds the row matching the prospect’s phone number
  2. Update that row with new data
    • Add Module: “Google Sheets” → “Update a Row”
    • Set “Row Number” to the row number returned from the search
    • Map the fields you want to update (lead status, interest score, etc.)
Irelia.ai Make.com integration guide, Advanced Automations, Search and Update Existing Records. Shows a Scenario canvas with three modules, Webhooks Custom webhook, Google Sheets Search Rows, and Google Sheets Update a Row, the last two highlighted with red arrows pointing up at them. This three-module pattern is how the reader updates an existing lead's row instead of creating a duplicate one.

Three-Module setup: Webhook → Search Rows → Update a Row

Result: Instead of creating duplicate rows, your existing lead’s information gets updated in place.
Phone number format must match. For the search to work, the phone number format in your existing records must match the format Irelia sends. Irelia sends phone numbers with the international prefix (e.g., 393401234567). If your existing records store phone numbers without the prefix (e.g., 3401234567), the search won’t find a match — because 3401234567 and 393401234567 are technically different values. Store phone numbers with the international prefix in your spreadsheets and CRMs. If you have existing records without prefixes, update them to include the prefix.
Same logic applies to CRMs. Most CRMs (HubSpot, Salesforce, Pipedrive) have similar “Search/Find Contact” and “Update Contact” Modules. Search by phone number, then update with the new data. Some CRMs even offer “Create or Update” Modules that handle both scenarios automatically.

Using Filters to Control When Actions Run

Filters let you add conditions so your action doesn’t run for EVERY event. Example: Only add to CRM if the prospect’s budget is “$10k-50k” or higher
  1. Right-click on the connection line between your webhook and action Modules
  2. Select “Set up a filter”
  3. Set your condition:
    • Label: “Budget Filter”
    • Condition: customVariables[].value → “Text operators: Contains” → $10k
  4. Click “OK”
  5. Only leads meeting this criteria will continue to your action
Irelia.ai Make.com integration guide, Advanced Automations, Using Filters to Control When Actions Run. Shows the Set up a filter dialog with an empty Label field, a Condition row mapped to the customVariables valueRaw tag, the operator set to Text operators Contains, and the comparison value entered as 10K. Note: the article's example condition is written with a dollar sign as in dollar-10k, but the value actually typed in this screenshot's filter is 10K without a currency symbol.

Filter configuration on the customVariables value field

The filter appears as a small funnel icon on the connection line.
Irelia.ai Make.com integration guide, Advanced Automations, Using Filters to Control When Actions Run. Shows the Scenario canvas with Webhooks, Google Sheets and Slack modules connected, and a small funnel-shaped filter icon sitting on the connector line between the Webhooks and Google Sheets modules, pointed out by a red arrow. This funnel icon is the visual sign that a condition is now controlling whether the action module runs.

Funnel icon on the connection line indicates an active filter

Common filter use cases:
  • Only add to CRM if budget matches your target → customVariables[].value equals $10k-50k
  • Only notify team if company size is “Enterprise” → customVariables[].value contains Enterprise
  • Only send to sales if lead is qualified → leadQualification equals fit
Use the value field (the categorized answer) for filters rather than valueRaw (exact words). The categorized value is more consistent and reliable for matching conditions.

Multi-Step Scenarios

Why do one thing when you can do several? Example: When a lead is qualified:
  1. Add to HubSpot CRM
  2. Send Slack notification to sales team
  3. Add to “Hot Leads” Google Sheet
  4. Send welcome email
How to set this up:
  1. After your first action Module, hover over its right edge and click the + icon
  2. Select your second app and action
  3. Configure the Module
  4. Repeat for additional actions
Modules run left-to-right. If an earlier Module fails, later ones won’t run unless you configure error handling. Place your most critical action first.

Using Routers for Conditional Logic

Routers let you create branching logic based on data — similar to “Paths” in other automation tools. Example: Route leads based on qualification status
  • If leadQualification equals "fit" → Route 1: Add to HubSpot + Notify sales
  • Else If leadQualification equals "not a fit" → Route 2: Add to nurture campaign
  • Else ("TBD") → Route 3: Add to “Needs Review” spreadsheet
How to set this up:
  1. After your webhook Module, click the + icon
  2. Search for and select “Router” (under Flow Control or Tools)
  3. The Router will show multiple output paths
  4. Click + on each path to add Modules
  5. Set up filters on each path’s connection to control which data flows where
Irelia.ai Make.com integration guide, Advanced Automations, Using Routers for Conditional Logic. Shows a real Scenario named CRM_IRELIA Da SITO WEB to Nuovo Lead in cerca di Partner, with Webhooks, Airtable Search Records, Gmail Send an email and Telegram Bot modules feeding into a Router that branches toward an Airtable Update a Record path labeled Lead già esiste and an Ignore path, plus usage stats and a run history panel on the right. This example shows how a Router can send leads down different paths depending on whether they already exist in the system.

Router Module with three output paths for conditional lead routing

Using Built-in Tools for Data Transformation

Make.com has built-in functions that let you transform data before sending it:
  • 🔢 Format phone numbers consistently (add country code)
  • ✂️ Split userName into first name and last name using text functions
  • 📊 Convert interestScore from decimal (0.85) to percentage (85%) using math functions
  • 📅 Change date formats to match your CRM using date functions
To use these, click into any field and then click the function icon (ƒ) to access Make.com’s built-in functions.
Irelia.ai Make.com integration guide, Advanced Automations, Using Built-in Tools for Data Transformation. Screenshot of the Irelia: New Contact → Google Sheet Scenario with the Google Sheets module settings open on the right and the function picker panel open next to a field, with a red box and arrow on the row of function category tabs and the Text and binary functions tab selected, listing functions such as length, lower, capitalize, replace, split and trim. The reader uses these tabs to find the text, math or date function needed to transform Irelia data before it reaches the destination.

The function picker panel for transforming data before sending

Real-World Use Case Examples

Use Case 1: Qualified lead fast track

Trigger: Lead Qualified Modules:
  1. Create contact in HubSpot with “Hot Lead” status
  2. Send Slack notification to sales team
  3. Add to “Qualified Leads” Google Sheet
  4. Send welcome email via Gmail
Impact: Sales team engages qualified leads within minutes instead of hours.

Use Case 2: Disqualified lead nurture

Trigger: Lead Disqualified Modules:
  1. Add to Mailchimp nurture campaign
  2. Log in “Nurture Pipeline” spreadsheet
  3. Create task in Asana to follow up in 3 months
Impact: No lead is wasted; everyone gets appropriate follow-up.

Use Case 3: Knowledge gap tracking

Trigger: Question Lacking Answer Modules:
  1. Send Slack notification to content team so they can reply manually through the Irelia dashboard
  2. Log in “Knowledge Base Gaps” spreadsheet
Impact: Continuously improve your AI agent’s Knowledge Base.

Use Case 4: Goal achievement flow

Trigger: Goal Achieved Modules:
  1. Send confirmation email with next steps
  2. Update CRM with goal completion
  3. Notify account manager in Slack
Impact: Instant positive reinforcement and seamless customer journey.

Use Case 5: Rich data capture

Trigger: Data Gathered Modules:
  1. Update CRM with custom variables (budget, timeline, company size)
  2. Router to add to segment-specific sheet (Enterprise vs. SMB)
  3. Trigger personalized email based on answers
Impact: Rich prospect data flows automatically; no manual entry.

💻 Make.com-Specific Tips

Instant vs. scheduled Scenarios

For webhook-triggered Scenarios, Make.com runs them instantly when data is received. However, you can also set up scheduled checks if needed. To verify your Scenario runs instantly:
  1. Click the three dots menu → “Scheduling”
  2. Ensure it’s set to run when triggered by webhooks

Operations and limits

Make.com charges based on operations (each Module execution = 1 operation). Plan accordingly:
  • A 3-Module Scenario uses 3 operations per run
  • Free tier: ~1,000 operations/month
  • Monitor your usage in your dashboard

Error handling

Make.com has powerful error handling options:
  1. Right-click on any Module → Select “Add error handler”
  2. Choose how to handle failures (ignore, retry, alert, etc.)
  3. This prevents one failure from stopping your entire Scenario
Irelia.ai Make.com integration guide, section Make.com-Specific Tips, Error handling. Shows the right-click context menu titled Error Handlers on a Module connector, listing the options Break, Commit, Ignore, Resume and Rollback, positioned near the Webhooks module with the Slack module visible at the top of the canvas. Choosing one of these options here decides how the Scenario reacts if a single Module fails during a run.

Error handling options for controlling Module failure behavior

Final Tips

  • 🎯 Start simple — One event, one action. Master that before expanding.
  • 🧪 Test thoroughly — Always use “Run once” to verify with real data before activating.
  • 📊 Monitor regularly — Check Scenario History weekly, especially at first.
  • 🔄 Iterate — Your first automation doesn’t have to be perfect. Refine over time.
  • 💾 Save often — Click the save icon after every change to avoid losing work.
  • 🤝 Ask for help — Both Irelia and Make.com have great support teams and communities.
Remember: every automation expert started with one simple Scenario. You just built yours. The possibilities from here are endless. Happy automating! 🚀

✅ Quick Checklist

Use this to verify your setup is complete:

Essential Setup

  • Webhook created in Make.com
  • Webhook URL copied from Make.com
  • URL pasted into Irelia for your chosen event
  • Test data sent from Irelia
  • Data structure determined in Make.com (“Successfully determined”)
  • Action Module configured (Google Sheets, Slack, or CRM)
  • “Run once” test completed successfully
  • Scenario turned ON
  • Scenario given a descriptive name
  • Scenario saved
  • Triggered a real event (or used the “Test” button)
  • Confirmed data appeared in destination app
  • Checked Scenario History shows successful run
✅ All checked? You’re good to go!

🛠️ Troubleshooting & FAQs

Don’t panic! Here are the most common issues and exactly how to fix them.
How to fix it:Step 1: Verify the webhook URL in Irelia
  • Go to Irelia → “Events and Notifications”
  • Check that the webhook URL is filled in for your event
  • Make sure it matches EXACTLY the URL from Make.com (no extra spaces)
Step 2: Send test data again
  • Click the blue “Test” button in Irelia next to your webhook URL
  • Wait 5–10 seconds
  • Go back to Make.com — the webhook should show “Successfully determined”
Step 3: Try a fresh webhook URL
  • If still not working, click on your webhook Module in Make.com
  • Create a new webhook with the “Add” button
  • Copy the new URL and paste it into Irelia
  • Click “Test” again in Irelia
How to fix it:Step 1: Read the error message
  • Click on the failed Module (shown with a red indicator)
  • Make.com shows detailed error messages in the execution details
  • Look for phrases like “Required field missing” or “Invalid credentials”
Irelia.ai Make.com integration guide, Troubleshooting, Issue 2, Read the error message. Shows a real Scenario named CRM_IRELIA Da BUBBLE to Nuova Free Trial with Webhooks, Router, Airtable and Telegram Bot modules, where the Airtable Create a Record step is flagged in red with a RuntimeError reading Value null is not a valid record ID, and the execution log on the right lists each completed step down to the failed Airtable-Create a Record entry. This is a more complex real-world example of the error-message reading skill described in the surrounding troubleshooting text.

Module error detail view with key diagnostic information

Step 2: Check required fields
  • Open your action Module configuration
  • Look for fields marked as required
  • Make sure each required field has data mapped
Step 3: Reconnect your account
  • In your action Module, click on the connection dropdown
  • Select “Add” to create a new connection
  • Sign in again and grant permissions
  • Run once to test again
Step 4: Verify your destination exists
  • Google Sheets: Confirm the spreadsheet wasn’t deleted or renamed
  • Slack: Check the channel wasn’t archived
  • CRM: Verify pipeline/status values still exist
How to fix it:Step 1: Check Scenario History for details
  • Go to your Scenario → “History” tab
  • Click on your recent run to expand details
  • Look at the output data from each Module
Irelia.ai Make.com integration guide, Troubleshooting, Issue 3, Check Scenario History for details. Shows the Irelia: New Contact to Google Sheet Scenario's History tab with a successful run timestamped 27 gennaio 2026, 18:24:59, and the Slack module's execution details expanded on the right showing the Input message text and the Output bundle with Timestamp, Channel and Message fields. Expanding a run like this lets the reader see exactly what output each Module produced, even when the result is not obvious from the destination app.

Expanded Scenario History run with output data from each Module

Step 2: Look in the right place
  • Google Sheets: Scroll to the bottom (new rows are added at the end). Try Ctrl+F to search.
  • Slack: Check you’re in the right channel. Search for messages from “Make.”
  • CRM: Search by phone number instead of name. Check if you’re in a filtered view.
Step 3: Check for filters
  • Go back to your Scenario editor
  • Look for any filter Modules (funnel icons) between your webhook and action
  • Click on the filter to verify your data passes the conditions
How to fix it:Step 1: Check if your Scenario is ON
  • Open your Scenario
  • Look at the toggle at the bottom left
  • If it shows “OFF”, turn it back on
Step 2: Check scheduling
  • Click the three dots menu → “Settings”
  • Make sure “Scheduling” is set to “Immediately” (not scheduled for specific times)
  • For real-time webhooks, the Scenario should run “On demand”
Step 3: Check authentication
  • Look for any warning icons (⚠️) on your Modules
  • Reconnect any apps that show warnings
  • This is especially common with Google accounts after password changes
Step 4: Verify Irelia configuration
  • Go to Irelia → “Events and Notifications”
  • Confirm the webhook URL is still there and correct
Step 5: Check Make.com operations usage
  • Go to your Make.com dashboard → “Organization” → “Operations”
  • Free plans have limited operations per month
  • If you’ve hit the limit, upgrade or wait for reset
How to fix it:Step 1: Audit your Scenarios
  • Check all your active Scenarios
  • Look for duplicates with the same webhook trigger
  • Turn off or delete duplicate Scenarios
Step 2: Check Irelia configuration
  • Verify each event has a UNIQUE webhook URL
  • If you pasted the same URL in multiple events, that’s the problem
Step 3: Check for multiple triggers
  • In your Scenario, ensure you only have ONE webhook Module
  • Multiple triggers can cause duplicate processing
How to fix it:Step 1: Use the right event
  • “New Inbound Contact” fires BEFORE data collection
  • Use “Data Gathered”, “Goal Achieved”, or “Lead Qualified” events instead if you need collected data
Step 2: Check variable indices
  • Custom variables are in an array (1, 2, 3, etc.)
  • Make sure you’re mapping the correct index
  • Use the data picker to navigate the array structure
Step 3: Test with a complete conversation
  • Instead of using the “Test” button, have a full conversation that reaches data collection
  • Then check if data flows through

🆘 Need Help?

Irelia.ai Support:
  • Contact support in the WhatsApp priority support group or send an email to info@irelia.ai
  • Include: screenshots of your configuration, the error message, and what you expected vs. what happened
Make.com Support: