Every 10 minutes

Get new Salesloft leads in Slack

New people added to Salesloft show up in Slack within 10 minutes, with their title and account.

Runs: Every 10 minutes
Apps: Salesloft
AI: Not needed
Access: read people

Send this to your assistant

Create a ClickRuntime automation: every 10 minutes, check Salesloft for newly added people and post each one's name, title and account to #new-leads in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

New people enter Salesloft from several places: CRM syncs, imports a marketer uploaded, a rep adding a prospect by hand, and integrations that push in contacts from events. Nobody on the team has a single view of that flow. A rep waiting for a list of webinar attendees does not know it has arrived, and a manager has no idea that 400 people were added overnight or that a sync has been quietly adding duplicates of existing contacts.

Every ten minutes the automation lists people in Salesloft sorted by created date, skips those it has already announced, and posts the new ones to a chat channel with name, company and owner. It remembers what it has seen, so each person is reported once. Sales development leads and sales operations people use it to watch what enters their prospecting system.

What you get out of it

Fresh leads get contacted sooner
When a new person is posted as soon as they exist, a rep can add them to a cadence the same morning. Waiting a day or two for someone to notice an import means interest has faded.
Sync problems show up early
An unexpected burst of new people can mean a CRM sync loop or a bad import. Spotting that within ten minutes lets operations stop it before thousands of unwanted records fill the system.
Owners know what they were assigned
Assignment rules put new people into reps' queues silently. A channel post tells the owner there is new work waiting, rather than leaving them to discover it when they next open their task list.
Imports are confirmed
After uploading a list, the marketer or ops person can watch the channel to see the contacts appear. That confirmation avoids repeating the upload by mistake and creating duplicate records.
A running history of intake
Scrolling through the channel shows when and how many people were added over a week. It provides a simple record to compare against campaign dates when explaining a change in pipeline numbers.

How it works

What happens, step by step

Every 10 minutes, ClickRuntime checks Salesloft for the most recently added people.
It keeps only people added since its last check, so nobody is announced twice.
Each new person is posted to #new-leads in Slack with their name, job title and company, oldest first.

Before it runs live

Connect Salesloft

What you get

RunsEvery 10 minutes

Get new Salesloft leads in Slacktoday, 9:00Succeeded

Slack · #new-leadsNew person: Priya Shah, VP Operations at Northwind Traders

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Salesloft steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

new_person_alert_salesloft.pyexample

from clickruntime import on_trigger, credentials, notify, http, state, report_fetched

@on_trigger
def run(event):
    token = credentials.connection("salesloft", "work")
    since = state.get("last_created_at") or ""
    resp = http.get("https://api.salesloft.com/v2/people",
                    params={"sort_by": "created_at", "sort_direction": "DESC", "per_page": 50},
                    headers={"Authorization": f"Bearer {token}"})
    resp.raise_for_status()
    people = [p for p in resp.json()["data"] if p["created_at"] > since]
    report_fetched(len(people))
    if not people:
        return {"posted": 0}
    for p in reversed(people):
        notify.slack(
            f"New person: {p.get('first_name', '')} {p.get('last_name', '')}, "
            f"{p.get('title') or 'no title'} at {p.get('person_company_name') or 'unknown account'}",
            channel="#new-leads",
        )
    state.set("last_created_at", people[0]["created_at"])
    return {"posted": len(people)}

FAQ

Common questions

Will existing people be announced when I first turn it on?

No. The first run sets the starting point, and only people created afterward are announced. If you want a one-time listing of existing contacts, ask for a separate export instead of letting the alert flood the channel.

Does it report people added through the CRM sync?

Yes. Any person record with a created date after the last check is included, whatever its source. The post can show where it came from if Salesloft records an import source or owner for the person.

Can the alert be limited to a team or tag?

Yes, a filter can restrict the alert to people with a certain owner, tag or account. For example, a regional manager could watch only people assigned to EMEA reps, keeping the channel focused. A regional manager might watch only one owner's people, while ops watches everything created by an import.

What permissions does it need?

read people. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Every 10 minutes