On a schedule

Post daily signup numbers to Slack and Microsoft Teams

Every morning, yesterday's signups are posted to the same channel in both Slack and Teams.

Runs: On a schedule
Apps: Microsoft Teams, Slack
AI: Not needed
Access: chat:write; ChannelMessage.Send

Send this to your assistant

Create a ClickRuntime automation: every morning at 9, post yesterday's signup numbers to #metrics in Slack and to our Metrics channel in Teams.

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

After an acquisition or a merger, one half of the company uses Slack and the other uses Microsoft Teams. Daily metrics end up posted in only one of them, so half the company never sees them, or someone copies the numbers across every morning.

Sending the same message to both keeps the whole company looking at the same figures without anyone acting as the go-between. It also works for alerts that both groups need to see at once.

What you get out of it

One set of numbers for everyone
Both groups see exactly the same figures at the same time. Discussions start from shared facts rather than "which number are you looking at?".
Nobody relays messages by hand
Copying a post from one chat app to another is a small daily task that gets forgotten. Here it is done every morning without anyone thinking about it.
Works while teams are split
Moving everyone onto one chat app can take months. This keeps information flowing in the meantime without forcing a switch.
A daily habit around the numbers
A message at the same time every day becomes something people look for. Small changes in signups are noticed early instead of at the monthly review.

How it works

What happens, step by step

Every morning at 9, ClickRuntime fetches yesterday's signup count from your data source.
It writes one short message with the number and the change from the day before.
The message is posted to your Slack channel.
The same message is posted to your Microsoft Teams channel.

Before it runs live

Connect Microsoft Teams
Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)

What you get

RunsOn a schedule

Post daily signup numbers to Slack and Microsoft Teamstoday, 9:00Succeeded

Slack · #metricsSignups on Sun 18 Oct: 214 (+19 vs previous day)

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

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Google Sheets
Combine it with other Microsoft Teams and Slack 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.

send_the_same_report_or_alert_to_slack_and_teams.pyexample

from datetime import date, timedelta
from slack_sdk import WebClient
from clickruntime import on_trigger, credentials, http

STATS_URL = "https://admin.example.com/api/signups"
TEAM_ID, CHANNEL_ID = "your-team-id", "your-channel-id"

@on_trigger
def run(event):
    day = date.today() - timedelta(days=1)
    key = {"Authorization": f"Bearer {credentials.secret('STATS_API_KEY')}"}
    today_n = http.get(STATS_URL, params={"date": day.isoformat()}, headers=key).json()["count"]
    prev_n = http.get(STATS_URL, params={"date": (day - timedelta(days=1)).isoformat()}, headers=key).json()["count"]
    text = f"Signups on {day:%a %d %b}: {today_n} ({today_n - prev_n:+d} vs previous day)"
    WebClient(token=credentials.connection("slack", "work")).chat_postMessage(channel="#metrics", text=text)
    http.post(f"https://graph.microsoft.com/v1.0/teams/{TEAM_ID}/channels/{CHANNEL_ID}/messages",
              headers={"Authorization": f"Bearer {credentials.connection('microsoft', 'work')}"},
              json={"body": {"content": text}})
    return {"signups": today_n}

FAQ

Common questions

Where do the signup numbers come from?

From any source with an HTTPS API, such as your app's own admin endpoint, your billing system or your analytics. The script fetches yesterday's count from there.

Can I add more numbers than signups?

Yes. Revenue, trials, cancellations or support tickets can be added to the same message, as long as each comes from a source with an API.

Can the messages be formatted differently in each app?

Yes. Slack and Teams each get their own version of the message, so you can use bold text, links or a short table that suits each app.

What permissions does it need?

chat:write; ChannelMessage.Send. 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 runs (on a schedule). Checks that find nothing to do 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.

On a scheduleAI