Hourly

Post new Wave customers to Slack

When a customer is added in Wave, their details appear in Slack within the hour.

Runs: Hourly
Apps: Wave
AI: Not needed
Access: full access token

Send this to your assistant

Create a ClickRuntime automation: every hour, look for customers added in Wave since the last check and post each one's name and email 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

In Wave a customer record can appear from several directions: you add one while drafting an invoice, a bookkeeper imports a list, or an online payment form creates one. Nobody else on the team hears about it. The person handling onboarding emails, contracts or the welcome call only finds out when the customer writes in asking why nothing has happened since they agreed to work together.

Once an hour the automation queries your Wave customers, compares their IDs with the list it remembers, and posts each new customer to Slack with the name and email address. It records the new IDs afterward so each customer is announced one time only, even if you edit the record later.

This is a good fit for agencies and consultancies where a new customer in the books should trigger a human follow-up, such as a welcome message or a kickoff call.

What you get out of it

Onboarding starts when the record exists
A Slack message the same hour a customer is added means the welcome email or call is scheduled right away, which keeps the first impression prompt for someone who has just agreed to pay you for your work.
Sales and delivery stay in sync
The person who closed the deal often creates the customer record, and the person who delivers the work never sees it. The channel closes that gap without a separate handoff message that somebody has to remember to write.
Catches records created by import
When a bookkeeper imports twenty customers from a spreadsheet, each one appears in the feed. You can spot duplicates or typos in names right away rather than at invoice time, when correcting them is more awkward.
Early check on data quality
Seeing name and email in the post makes mistakes visible: a missing email address, a company entered as a person. Fixing it before the first invoice avoids bounced invoice emails and a delayed payment.
A simple log of customer growth
Scrolling the channel shows how many customers were added each month, a rough growth signal that does not need a report, a spreadsheet or someone to count records inside Wave.

How it works

What happens, step by step

Every hour ClickRuntime checks your customer list in Wave.
It compares the list with the customers it has already seen, so each one is posted only once.
Each new customer's name and email goes to your Slack channel.

Before it runs live

Connect Wave

What you get

RunsHourly

Post new Wave customers to Slacktoday, 9:00Succeeded

Slack · #salesNew Wave customer: Northwind Traders (accounts@northwind.example)

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 Wave 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_customer_alert.pyexample

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

BUSINESS_ID = "your-wave-business-id"

def wave(query, variables=None):
    token = credentials.connection("wave", "work")
    resp = http.post("https://gql.waveapps.com/graphql/public", headers={"Authorization": f"Bearer {token}"},
                     json={"query": query, "variables": {"biz": BUSINESS_ID, **(variables or {})}})
    return resp.json()["data"]["business"]

QUERY = """query($biz: ID!) { business(id: $biz) { customers(page: 1, pageSize: 50, sort: [CREATED_AT_DESC]) {
  edges { node { id name email createdAt } } } } }"""

@on_trigger
def run(event):
    customers = [e["node"] for e in wave(QUERY)["customers"]["edges"]]
    seen = state.get("customer_ids")
    new = [c for c in customers if seen is not None and c["id"] not in seen]
    report_fetched(len(new))
    if seen is not None and not new:
        return {"posted": 0}
    for c in new:
        notify.slack(f"New Wave customer: {c['name']} ({c.get('email') or 'no email'})", channel="#sales")
    state.set("customer_ids", list(set(seen or []) | {c["id"] for c in customers}))
    return {"posted": len(new)}

FAQ

Common questions

How does it avoid announcing my existing customers?

On the first run it stores the IDs of customers already in Wave and posts nothing. From the second run on, only IDs it has not seen before are announced, so your current customer list stays quiet and the channel only receives genuinely new people.

Is a customer imported from a CSV announced as well?

Yes. The check looks at the customer list itself, not how a record was created, so imported customers appear in the feed on the next hourly run, one message each. A large import therefore produces a burst of posts.

Can the message include the customer's phone number or address?

Wave stores those fields on the customer record, so they can be added to the Slack message if you want them. Tell your AI assistant which fields to include, and consider whether the channel is an appropriate place for contact details.

What permissions does it need?

full access token. 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 15 minutes