The moment it happens

Post new Outreach prospects to Slack

As soon as a prospect is created in Outreach, #sdr-team sees their name, company and owner.

Runs: The moment it happens
Apps: Outreach
AI: Not needed
Access: prospects.read, webhooks

Send this to your assistant

Create a ClickRuntime automation: when a prospect is created in Outreach, post their name, company and owner to #sdr-team 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

A founder-led sales team imports leads into Outreach from events, partners and a signup form, and some of those prospects matter more than others: a VP at a target account, a referral from a customer, a person who just requested a demo. The rep who should call first has no idea the prospect exists until they open a sequence list. Warm leads in a CRM lose value by the hour, and a prospect who filled out a form at noon should not be contacted on Thursday.

When a prospect is added in Outreach, the event reaches ClickRuntime immediately. The prospect record is fetched, with name, title, company, email, tags and the owner who got it, and a message goes to Slack so the right person sees the new lead the moment it exists.

It is helpful for inbound teams, event follow-up, partner referrals and anywhere speed to lead is a priority.

What you get out of it

Hot leads are contacted quickly
A rep who sees a new demo request in Slack can call or write within minutes. Fast follow-up is a lever you control entirely, and this makes it practical. That attention can decide whether a prospect becomes a customer or a missed chance.
Important prospects are never lost in a list
A VP at a target account stands out in a channel post in a way that a row in a long import never does, so high-value people get personal attention.
Event leads do not go cold
Imports after a conference add hundreds of prospects at once, and flagging the ones with certain tags helps reps pick out the people they actually met. That is a sensible way to keep the best conversations from being buried in a large batch of new names.
Ownership gaps are noticed
If a prospect arrives without an owner, the post makes that obvious. A manager can assign them straight away instead of discovering them weeks later. Assigning an owner quickly keeps the lead from being forgotten while it is still fresh.
Everyone knows where leads come from
Seeing a stream of new prospects, with source tags, shows which campaigns and partners are delivering. It supports decisions about where to spend the next marketing dollar. That feedback loop is difficult to get from a spreadsheet exported at the end of the quarter.

How it works

What happens, step by step

Each time a prospect is created in Outreach, Outreach tells ClickRuntime straight away.
The automation looks up the prospect's name, company and owner.
A message goes to #sdr-team, like "New prospect: Priya Shah at Northwind Traders (owner Morgan)".

Before it runs live

Connect Outreach
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Post new Outreach prospects to Slackjust nowSucceeded

Slack · #sdr-teamNew prospect: *Priya Shah* at Northwind Traders (owner Morgan)

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 Outreach 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_prospect_alert.pyexample

from clickruntime import on_event, credentials, http, notify

@on_event
def handle(event):
    body = event.json or {}
    if body.get("meta", {}).get("eventName") != "prospect.created":
        return {"skipped": body.get("meta", {}).get("eventName")}
    resp = http.get(f"https://api.outreach.io/api/v2/prospects/{body['data']['id']}", params={"include": "owner"},
                    headers={"Authorization": f"Bearer {credentials.connection('outreach', 'work')}"})
    resp.raise_for_status()
    p = resp.json()
    a = p["data"]["attributes"]
    owner = next((i["attributes"]["name"] for i in p.get("included", []) if i["type"] == "user"), "unassigned")
    notify.slack(f"New prospect: *{a.get('firstName', '')} {a.get('lastName', '')}* at {a.get('company') or '-'} (owner {owner})",
                 channel="#sdr-team")
    return {"prospect": p["data"]["id"]}

FAQ

Common questions

Will a large import flood the channel?

It can, because each added prospect triggers an event. You can filter by tag or source so only certain prospects are posted, or collect a bulk import into a single summary message. Grouping the batch keeps the channel readable.

Does it post prospects created by sequences or API too?

Any prospect created in Outreach triggers the event, whether it was added by hand, by import or through an integration. A filter on the source or owner can limit posts to the ones you care about.

What does the post include?

Name, title, company, email address, tags and the assigned owner, plus a link to the prospect in Outreach. Personal data is kept to what a rep needs to start the conversation. Nothing sensitive beyond that is shared.

What permissions does it need?

prospects.read, webhooks. 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 for each event the app sends.

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.

The moment it happens