The moment it happens

Hear about every Keap payment as it lands

When a customer pays, Slack shows who paid and how much.

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

Send this to your assistant

Create a ClickRuntime automation: each time a payment is recorded in Keap, post the customer name and amount to #sales 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 bookkeeper or owner who runs invoicing in Keap often learns that a customer paid only by logging in and scanning the order list, or by checking the bank feed days later. Meanwhile a client whose payment cleared on Tuesday is still receiving reminder emails on Thursday, and the person who should start the work is waiting for confirmation that never reaches them.

As soon as Keap records a payment, Keap notifies ClickRuntime, which fetches the payment details and posts a message to Slack with the amount, the contact it belongs to and the invoice or order it applies to. The team sees the money arrive while it is still news, without anyone running a report.

It works well for coaching programs, agencies and course sellers who take payments throughout the day and want the right person to know at once.

What you get out of it

Work starts as soon as money lands
If delivery depends on payment, such as onboarding a new client or sending course access, a Slack post tells the responsible person right away. Customers who paid are not left waiting while the team assumes payment is pending.
Reminders stop going to people who paid
When the finance owner sees a payment appear, they can pause a collections email or call before it goes to a customer who already settled. That protects a relationship you just spent effort winning.
Small wins are visible to the team
Salespeople and coaches like seeing proof that payments are coming in. A running feed of amounts builds a sense of momentum without anyone having to compile a summary. It also gives your team a reason to talk about what is working.
Odd amounts get questioned quickly
A payment for a different amount than expected, or one that appears twice, is obvious when it is posted as it happens. Fixing a mistake the same day beats finding it during month-end reconciliation.
Reconciliation has a timestamped trail
The Slack channel becomes a dated list of payments with contact names, which you can compare against Keap and your bank statement when the books are closed. It narrows down where a discrepancy began.

How it works

What happens, step by step

When a payment is recorded against an invoice in Keap, Keap tells ClickRuntime straight away.
ClickRuntime looks up the payment amount and the customer who paid.
It posts a one-line message to #sales in Slack with the customer's name and the amount paid.

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

Hear about every Keap payment as it landsjust nowSucceeded

Slack · #salesPayment: Dana Reyes paid $1,250.00

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_payment_invoice_alert.pyexample

from clickruntime import on_event, credentials, notify, http

API = "https://api.infusionsoft.com/crm/rest/v1"

@on_event
def handle(event):
    headers = {"X-Keap-API-Key": credentials.secret("KEAP_PAT")}
    for obj in (event.json or {}).get("object_keys", []):
        tx = http.get(f"{API}/transactions/{obj['id']}", headers=headers).json()
        contact = http.get(f"{API}/contacts/{tx['contact_ids'][0]}", headers=headers).json()
        notify.slack(f"Payment: {contact.get('given_name', '')} {contact.get('family_name', '')} "
                     f"paid ${tx['amount']:,.2f}", channel="#sales")
    return {"posted": len((event.json or {}).get("object_keys", []))}

FAQ

Common questions

Does it post payments, invoices or both?

The automation is built around payment events, so a message is posted when Keap records a payment. An invoice that has been created but not paid does not trigger it. If you also want a note when an invoice is issued, that can be handled as a second alert.

Will refunds or failed payments show up as well?

Only successful payments are posted by default. Refunds and failed charges are separate situations in Keap, and mixing them into the same channel could be confusing. You can ask for a distinct message for those cases, ideally in a different channel.

Can it post only payments above a certain amount?

Yes. A common version posts every payment under a threshold quietly and highlights anything above, for example $1,000, so large deals stand out. You describe the cutoff to your assistant, review the change, and approve it.

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