Every 15 minutes

Post new Apollo contacts to Slack

Within 15 minutes of a contact being added in Apollo, #prospects gets their name, title and company.

Runs: Every 15 minutes
Apps: Apollo.io
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every 15 minutes, check Apollo for newly added contacts and post each one's name, title and company to #prospects 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

An account executive lets marketing and a data-enrichment tool add contacts to Apollo all day. New people arrive from imports, list builds and the Chrome extension, with titles and companies attached. The AE only sees them when they open Apollo and sort by date, so a contact from a priority company can sit untouched for two days while a competitor reaches out first.

Every 15 minutes, ClickRuntime searches Apollo contacts sorted by creation date, skips any it has already seen and posts the new ones to Slack. Each message carries the name, title, company and a link to the record, so a rep can start outreach from the channel.

Teams that split territories can send it to a channel the owner of that region watches. A manager can also use the channel to watch how fast reps respond.

What you get out of it

Fresh contacts get contacted first
Speed to first touch matters in outbound. A message within fifteen minutes of a contact being added gives your team a head start over anyone else courting the same person.
Imports can be sanity checked
When a list of 300 contacts lands, the channel shows them arriving. A column of people with the wrong titles or an unexpected company reveals a bad import early. Fixing it takes a minute instead of a week.
Marketing and sales stay aligned
Marketing sees its additions acknowledged in the channel and sales sees what was added. The usual argument over whether leads were ever delivered gets shorter. The usual argument over whether leads were ever delivered gets shorter and calmer.
Owners find out they own something
When contacts are assigned automatically, the owner may never see the assignment. A Slack message puts the name in front of them with title and company already visible. That removes a common reason for leads going cold.
High-value titles stand out
Scanning a stream of names, a VP or Head of title catches the eye. Reps can flag the senior contacts for a personal message instead of a templated one. The best contacts get the best effort.
Reps can see volume trends
A day with 3 new contacts followed by one with 200 is visible in the channel without any reporting. You learn how list builds and imports are really feeding the pipeline, which helps when you plan targets.

How it works

What happens, step by step

Every 15 minutes, ClickRuntime checks Apollo for the most recently added contacts.
It skips any contact it has already posted.
Each new contact goes to #prospects with their name, job title and company.

Before it runs live

Connect Apollo.io

What you get

RunsEvery 15 minutes

Post new Apollo contacts to Slacktoday, 9:00Succeeded

Slack · #prospectsNew contact: *Priya Shah*, Head of 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 Apollo.io 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_contact_alert_apolloio.pyexample

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

@on_trigger
def run(event):
    resp = http.post("https://api.apollo.io/api/v1/contacts/search",
                     headers={"X-Api-Key": credentials.secret("APOLLO_API_KEY"), "Cache-Control": "no-cache"},
                     json={"sort_by_field": "contact_created_at", "sort_ascending": False, "per_page": 50})
    resp.raise_for_status()
    since = state.get("since") or ""
    new = [c for c in resp.json()["contacts"] if c["created_at"] > since]
    report_fetched(len(new))
    if not new:
        return {"new": 0}
    for c in reversed(new):
        notify.slack(f"New contact: *{c['name']}*, {c.get('title') or '-'} at {c.get('organization_name') or '-'}",
                     channel="#prospects")
    state.set("since", new[0]["created_at"])
    return {"new": len(new)}

FAQ

Common questions

Will it post contacts that existed before I turned it on?

No. The first run records the contacts it can see as already known, and only contacts created after that point are posted. That avoids a flood of old records in your channel on day one.

Can I limit it to certain titles or companies?

Yes. The search can include filters such as person titles, locations or labels, and your AI assistant can add a rule to post only contacts that match. Everything else is still skipped silently rather than shown.

What if two people add the same contact?

Apollo generally merges duplicates by email, so the contact is posted once. The alert tracks record IDs it has seen, which means an edit to an existing contact will not trigger a repeated message. So a changed title will not show up twice.

What permissions does it need?

read. 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 30 minutes