The moment it happens

Post new Keap contacts to Slack

Each new contact shows up in Slack with their name, email and where they came from.

Runs: The moment it happens
Apps: Keap
AI: Not needed
Access: PAT

Send this to your assistant

Create a ClickRuntime automation: when a contact is added in Keap, post their name, email and lead source to #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

In a Keap account, new contacts arrive from landing pages, web forms, imports, a sales rep typing one in after a call, or an integration pushing records through the API. Nobody is looking at the contact list all day, so a hot inquiry from a web form can sit untouched while a follow-up sequence sends it a generic welcome email. Sales teams only find out when a customer complains they never heard back.

When Keap creates a contact, it sends an event to ClickRuntime. ClickRuntime then fetches the full contact record, so the message has more than an ID, and posts name, email, phone and company details to the Slack channel you pick. The post goes out as the contact is created, not on a polling delay.

It is most useful for service businesses and coaches where the first reply decides who wins the job.

What you get out of it

First reply beats the competition
When someone fills in a quote request they often contact two or three providers. The one who answers first usually wins, and a Slack post seconds after Keap creates the contact gives your team that head start.
Reps see leads without opening Keap
Salespeople spend their day in calls and chat. A message in Slack with name, email and phone means they can reach out immediately instead of waiting until they next check the contact list.
Bad data gets caught early
If a form sends a contact with a missing email or an obviously fake name, someone reading the channel spots it the same day. Waiting for a monthly list cleanup lets junk contacts enter campaigns.
Ownership is decided in the open
Putting each new contact in a shared channel lets the team claim it with a reaction or a reply. That avoids the situation where three people each assumed someone else had already called.
You learn which sources produce contacts
Scrolling the channel gives a feel for how many contacts arrive per day and from which forms or imports. It helps you notice a sudden stop in sign-ups before a weekly report would.

How it works

What happens, step by step

When a new contact is added in Keap, Keap tells ClickRuntime straight away.
ClickRuntime looks up the contact in Keap to get their name, email address and lead source.
It posts the new contact to #leads in Slack.

Before it runs live

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

What you get

RunsThe moment it happens

Post new Keap contacts to Slackjust nowSucceeded

Slack · #leadsNew contact: Dana Reyes <dana@northwind.com> Lead source ID: 12 (Webinar)

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 Keap 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_keap.pyexample

from clickruntime import on_event, credentials, notify, http

@on_event
def handle(event):
    e = event.json or {}
    if e.get("event_key") != "contact.add":
        return {"posted": 0}
    headers = {"X-Keap-API-Key": credentials.secret("KEAP_PAT")}
    for obj in e.get("object_keys", []):
        c = http.get(f"https://api.infusionsoft.com/crm/rest/v1/contacts/{obj['id']}",
                     headers=headers, params={"optional_properties": "lead_source_id"}).json()
        email = (c.get("email_addresses") or [{}])[0].get("email", "no email")
        notify.slack(f"New contact: {c.get('given_name', '')} {c.get('family_name', '')} <{email}>\n"
                     f"Lead source ID: {c.get('lead_source_id') or 'none'}", channel="#leads")
    return {"posted": len(e.get("object_keys", []))}

FAQ

Common questions

Does it fire for contacts I import in bulk?

It depends on how Keap raises the event. Contacts created through an import can each generate an event, which would mean one Slack post per contact. If you regularly import large lists, ask for a filter or a single summary message so the channel does not flood.

What details from the Keap contact appear in the post?

The post is built from the contact record that ClickRuntime fetches after the event arrives, so it can include first and last name, email, phone number, company and the owner. Custom fields can be added if you tell your assistant which ones you want.

Which Keap account type do I need?

You need a Keap account that allows API access and event notifications, and the person connecting it must be able to authorize the connection. Keap's own plan and permission rules decide this. The credentials are saved as secrets and are not shown in the Slack message.

What permissions does it need?

PAT. 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