On a schedule
Post new Pipedrive contacts to Slack
Each new person is posted to Slack with their organization and owner.
- Runs
- On a schedule
- Apps
- Pipedrive
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: every 5 minutes, post new Pipedrive persons to #sales in Slack with their name, organization and owner.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Contacts enter Pipedrive from several places: a rep adding someone after a conference, a web form, an import or an integration. Yet nobody is told when a new person is added, so a hot inbound lead can sit in the list for days. The owner may be on vacation, the contact may belong to no one, and the prospect who wanted an answer quickly signs with whoever replied first.
On a schedule, persons are listed by add_time, and anyone added since the last remembered ID is posted to Slack. The newest ID is stored, so each check picks up only new contacts. People who track inbound interest or assign leads see every addition in one channel.
It helps teams that route inbound leads by hand and sales operations people who keep the contact database clean.
What you get out of it
Fast response to inbound contacts
When a new contact appears in Slack, someone can reach out within the hour. Speed to first reply is one of the strongest predictors of winning a lead. That speed is often the difference between winning and losing an inbound lead.
Unowned contacts get claimed
A contact added without an owner would otherwise be forgotten. Seeing it in a channel lets a manager assign it right away, before it goes cold. Assigning an owner on the spot keeps leads from falling between members of a busy team. Nothing sits waiting for someone to notice.
Catch bad data early
Duplicates, missing emails and odd names are easy to spot when each addition is visible. Cleaning up in the moment is easier than a large cleanup later. A small data fix right away prevents the slow decay of a CRM full of half-complete records. Clean data helps every report built on top of it.
Know where leads come from
A flow of new people shows which events and forms are working. When contacts from a webinar appear in bunches, the team can see its value directly. Marketing and sales can both see which activities fill the database, which makes planning the next event or campaign more grounded.
Only new people are posted
Each person appears once because the last ID is remembered. Edits to existing contacts do not cause repeats, so the channel stays readable. A readable channel keeps people paying attention, so a genuinely interesting contact is noticed immediately rather than buried.
How it works
What happens, step by step
Every five minutes, ClickRuntime checks Pipedrive for newly added people.
Each new person is posted to your Slack channel with their organization and owner.
It remembers the last person it posted, so each one appears only once.
Before it runs live
- Connect Pipedrive
What you get
Build your own
Need it to work differently?
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 Pipedrive steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched
API = "https://api.pipedrive.com"
@on_trigger
def run(event):
headers = {"Authorization": f"Bearer {credentials.connection('pipedrive', 'work')}"}
people = http.get(f"{API}/api/v2/persons", headers=headers, params={
"sort_by": "add_time", "sort_direction": "desc", "limit": 50}).json()["data"]
last_id = state.get("last_id")
new = [p for p in people if last_id is not None and p["id"] > last_id]
report_fetched(len(new))
if people:
state.set("last_id", max(p["id"] for p in people))
if not new:
return {"posted": 0}
users = {u["id"]: u["name"] for u in http.get(f"{API}/v1/users", headers=headers).json()["data"]}
for p in reversed(new):
org = http.get(f"{API}/api/v2/organizations/{p['org_id']}", headers=headers).json()["data"]["name"] if p.get("org_id") else "no organization"
notify.slack(f"New person: {p['name']} · {org} · owner {users.get(p['owner_id'], 'unknown')}", channel="#sales")
return {"posted": len(new)}FAQ
Common questions
Does it post people added by imports?
How often does it check?
Can I see which form or source the person came from?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Post won Pipedrive deals to Slack
Every won deal is posted to your wins channel with its name, value and owner.
See how it worksPost new Pipedrive deals to Slack
Your team sees each new deal's value and stage in Slack within minutes.
See how it worksCreate follow-ups when a lead replies with interest
When a lead replies, the email is checked for interest and a call is booked on the deal for the ones who want to talk.
See how it worksKeep exploring
Set up “Post new Pipedrive contacts to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
