Finding out about new leads shouldn’t mean living in your inbox or refreshing a dashboard all day. If you’re using Scrab for lead management, you’ve probably wondered if you can get notified—automatically—whenever a new lead shows up. The answer is yes, but like with most tools, you have to set it up right, or you’ll end up buried in useless pings.
This guide is for anyone who wants to cut out the noise and actually get useful, actionable notifications from Scrab. Whether you’re a solo founder, a sales manager, or just the person who drew the short straw and has to wrangle the leads, here’s how to set up notifications that help you work smarter—not just add to your digital clutter.
Why Bother With Automated Notifications?
Let’s be honest: most notification setups are a mess. Either you don’t get what you need, or you get so many updates you start ignoring them altogether. But when you dial it in, automated notifications for new leads can mean:
- Faster response times. The sooner you know, the sooner you can act.
- No more missed opportunities. You catch every hot lead, even if you’re not glued to Scrab.
- Cleaner workflow. No more endless dashboard refreshes or manual checks.
But if you’re not intentional, you’ll just end up with another noisy channel. So, let’s do this right.
Step 1: Decide What a “New Lead” Actually Means to You
Before touching any settings, get clear on what counts as a new lead. Scrab can pull in a lot of data, and not every row is worth an alert.
Things to consider: - Are you tracking all signups, or just qualified leads? - Should you only get notified for leads assigned to you, or for everyone? - Do you need to be alerted on every single lead, or just ones meeting certain criteria (e.g., high-value, from a specific region)?
Pro tip:
If you set notifications for every lead, you’ll quickly tune them out. Start with the most important ones, and expand if needed.
Step 2: Pick Your Notification Channel
Scrab offers a few ways to get notified. The main options (as of early 2024):
- Email notifications: The default. Easy, but gets lost if your inbox is already chaos.
- In-app alerts: Show up in Scrab itself. Useful if you’re logged in, pointless otherwise.
- Slack/Teams integration: Nice for teams who already live in Slack or Teams. Less context-switching.
- Webhook/Zapier: For the tinkerers—pipe leads into whatever system you want.
What actually works? - If you’re solo or in a small team, email is usually fine—if you filter it right. - For bigger teams or if you’re already using Slack, set up a dedicated channel. Don’t dump every notification into a general chat or you’ll annoy everyone. - Avoid SMS or push notifications unless you’re expecting very few leads, or you like being interrupted at dinner.
Step 3: Set Up the Notification Rule in Scrab
Scrab’s automation and notification features live in its settings or “Automations” tab. The interface changes sometimes, but the basic flow is:
- Go to Settings > Automations (or Notifications) in Scrab.
- Create a new automation.
- Look for a button like “Add Automation” or “New Notification.”
- Choose the trigger.
- Pick something like “When a new lead is created” or “When lead status changes to X.”
- Set the filter.
- This is where you narrow it down. For example:
- Only leads from certain sources
- Leads with a score above a certain threshold
- Only leads assigned to you (or your team)
- Pick the action.
- Send an email
- Post to Slack/Teams
- Call a webhook (for integrations)
-
Customize the message.
- Include key info: name, company, contact details, maybe the lead score.
- Don’t go overboard—nobody wants a 500-word notification.
-
Save and test your automation.
- Most mistakes happen here. Use Scrab’s “Send test notification” if it has one.
- Double-check who gets notified—no one wants their CEO getting every lead alert by accident.
Stuff to ignore:
- “Notify on all updates” rules. Unless you’re running a one-person shop, you don’t need to know every time a lead record changes.
- Overly broad triggers. Get specific, or prepare to mute the channel in a week.
Step 4: Connect to Your Preferred Channel
If you picked email, you’re basically done. For Slack, Teams, or other integrations, there’s a bit more setup.
For Slack
- In Scrab, select “Slack” as the action.
- You might need to connect your Slack account (OAuth flow).
- Choose the channel (create a new one like #new-leads—not #general).
- Set who should be notified—everyone or just a specific group.
- Save.
Pro tip:
Use Slack’s built-in notification settings to control when you actually get pinged. Don’t let Scrab override your preferences.
For Microsoft Teams
- Pick Teams as the action.
- Authorize Scrab to access Teams.
- Choose the team and channel.
- Save and test.
For Webhook/Zapier
- Choose Webhook as the action.
- Enter the webhook URL (from your app or Zapier).
- Map the data fields you want to send.
- Test it—don’t skip this step.
Heads up:
Webhooks are powerful, but also a quick way to create a notification storm. Only use them if you know what you’re doing.
Step 5: Test—and Don’t Skip This
Most notification setups break because nobody tests them before going live. Send a few test leads through and make sure:
- The right people are getting the right info.
- The alerts are readable, not cryptic.
- You’re not getting duplicates for the same lead.
If something’s off: - Go back and tweak your filters or message format. - Make sure integrations (like Slack) have the right permissions—sometimes messages get lost because Scrab isn’t fully authorized.
Step 6: Keep It Tidy (And Don’t Be Afraid to Prune)
Over time, it’s easy for notification rules to pile up, especially if multiple people are tinkering. Review your automations every month or so:
- Turn off or delete any rules you’re ignoring.
- Update filters as your lead criteria change.
- Check if people have left the company but are still getting alerts (it happens).
Real talk:
If you find yourself ignoring alerts, it’s a sign your setup is too noisy or not targeted enough. Less is more.
What Works, What Doesn’t, and What to Ignore
Works well: - Tight, targeted notifications (e.g., only high-quality leads) - Pushing to a dedicated Slack/Teams channel - Including just enough info for quick action
Doesn’t work: - Not testing before going live - Sending every update to everyone (guaranteed to cause alert fatigue) - Relying solely on in-app notifications (nobody checks them outside Scrab)
Ignore: - “AI-powered” notification settings unless you’ve actually seen them work in your workflow—they usually just add complexity. - Fancy formatting or emojis in alerts—clarity wins.
Keep It Simple, Iterate Often
Automated notifications can be a lifesaver—or just another distraction. Start with the basics: clear criteria, the right channel, and a message you’d actually want to read. Don’t be afraid to tweak or even turn things off if they’re not helping.
Remember, the goal is to be notified, not annoyed. Keep it simple, check in after a few weeks, and adjust as you go. The best notification setup is the one you barely have to think about.