by Noel Maniraguha on January, 2025
%20(airtable).png?width=1000&height=400&name=Notification%20for%20replies%20(client%20comms)%20(airtable).png)
This automation notifies your agency and clients about category changes, typically triggered when a lead replies, ensuring seamless communication updates. It also adds the lead data to Airtable.
Notification for replies (simple)
This automation has 2 components.
1. Notifying YOUR AGENCY about category changes (which usually occur when a lead replies).
2. Notifying YOUR CLIENTS about category changes (which usually occur when a lead replies).
Notification for replies (leads database)
This automation has 3 components.
1. Notifying YOUR AGENCY about category changes (which usually occur when a lead replies).
2. Notifying YOUR CLIENTS about category changes (which usually occur when a lead replies).
3. Logging all engaged leads within Airtable: duplicate the workspace here.
Insert the blueprint in make (new scenario)
Manual Changes
Smartlead Webhook Creation
Find it here and add a new webhook with the following settings:
Event Type: LEAD_CATEGORY_UPDATED
Choose any category (positive categories recommended)
Slack Incoming Webhook
Create one here and replace {SLACK_INCOMING_WEBHOOK} with your webhook URL
Why not use the built-in Slack integration? It won't notify you if you're the one posting the message.
Airtable errors to watch out for:
After connecting Airtable, you will need to choose the Base, Table, and View. It is important to note that each of these variables has underlying IDs; therefore, a "Grid view" from one base is not the same as a "Grid view" from another base.
Each Airtable module has all of the variables mapped. However, if you switch the table, you may notice that all variables are removed.
If this happens, I suggest you clone the Airtable module. Copy/paste each of the variables from one module onto the second module. Then delete the old module, after successfully adding the data to the new one that's within your base/table.
Set a schedule
I recommend choosing an "immediate" occurrence for this automation
