# A Slack message every morning, written from live data

Source: https://clickruntime.com/use-cases/daily-slack-message

> Tell your assistant what the message should say, which channel and when. ClickRuntime posts it every weekday at that time, filled in with numbers or items fetched fresh on each run.

## Can ChatGPT or Claude send me a Slack message every morning?

Not by themselves: they post only during a chat, and their own scheduled tasks answer inside the chat app, not in your Slack. With ClickRuntime connected, your assistant sets up an automation that runs every weekday at the time you choose, fetches what the message needs and posts it to your channel.

### Why the assistant can't do this on its own

- No clock. An assistant acts when you send it something. A 9:00 post needs a schedule that runs on its own.
- No lasting Slack connection. Posting to a channel every day needs a connection that stays in place after the chat ends.
- A fixed message is what Slack's own /remind does. A useful morning message has today's numbers in it, which means calling your tools' APIs on each run.

## Set it up from your AI assistant

Prompt to copy:

> Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.

1. **Connect ClickRuntime to your assistant.** Add ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
2. **Paste the prompt.** Start a new chat and paste: “Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.” Change the details (times, channels, addresses) to yours.
3. **Read the draft.** The assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
4. **Connect accounts and save keys.** Posting uses the workspace notifications Slack: the assistant gives you a link to connect it once in the ClickRuntime dashboard, then you invite the app to the channel. The Linear API key is saved as a secret in the ClickRuntime dashboard; the assistant gives you the link and never asks for the key in chat.
5. **Test it.** The assistant runs it once now so the message appears in the channel, and adjusts the wording until it reads the way you want.
6. **Turn it on.** The assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
7. **Check it in the ClickRuntime dashboard.** The automation page shows “Weekdays at 9:00 (Europe/Berlin)” and the next three run times. Each run shows what was posted, so you can check a past morning's message.

Connector setup for each assistant: https://clickruntime.com/assistants

## What the assistant writes

`morning_slack_post.py`

```python
from clickruntime import on_trigger, credentials, notify, http

CHANNEL = "#team"
QUERY = """
query { issues(filter: { team: { key: { eq: "ENG" } }, labels: { name: { eq: "Bug" } },
                         state: { type: { nin: ["completed", "canceled"] } } },
               orderBy: createdAt, first: 100) {
    nodes { identifier title url createdAt } } }
"""

@on_trigger
def run(event):
    key = credentials.secret("LINEAR_API_KEY")
    data = http.post("https://api.linear.app/graphql", json={"query": QUERY},
                     headers={"Authorization": key}).json()
    bugs = sorted(data["data"]["issues"]["nodes"], key=lambda i: i["createdAt"])
    oldest = "\n".join(f"• <{b['url']}|{b['identifier']}> {b['title']}" for b in bugs[:3])
    text = f"Good morning! {len(bugs)} open bugs in ENG."
    if oldest:
        text += f"\nOldest:\n{oldest}"
    notify.slack(text, channel=CHANNEL)
    return {"open_bugs": len(bugs)}
```

- The schedule and timezone live on the automation, not in the code. Changing the time is one message to your assistant.
- This is not a polling script: it does the same job every morning, so it doesn't call report_fetched.
- The Linear key is read with credentials.secret while the run is running, and is masked in logs.

## A schedule, not a trigger link

A schedule: weekdays at a time, in your timezone. ClickRuntime shows the next three run times before it goes live, so you can check daylight saving is right.

If the message should go out when something happens instead (a deploy, a sale), use a trigger link and have that service call it.

## Limits

- notify.slack posts to the channel you name in the workspace's notifications Slack. To post as yourself, the assistant uses a connected Slack account instead.
- Slack formatting is Slack's mrkdwn. Long messages are best kept under a few thousand characters.
- Schedules are every 5 minutes or slower; a daily post uses about 22 runs a month on weekdays.

## Troubleshooting

### The run fails with channel_required or not_in_channel.

Name the channel in the prompt, and invite the ClickRuntime notifications app to it in Slack.

### It posted at the wrong hour.

The timezone is probably wrong. Ask: “move my morning post to 9:00 Europe/Berlin”. The automation page shows the next run time to confirm.

### Linear returns 401.

The key saved in the ClickRuntime dashboard is wrong or revoked. Save a new one under the same name; no change to the script is needed.

## Related

- [Slack automations](https://clickruntime.com/apps/slack)
- [Linear automations](https://clickruntime.com/apps/linear)
- [Google Calendar automations](https://clickruntime.com/apps/google-calendar)
- [shopify-daily-orders](https://clickruntime.com/templates/shopify-daily-orders)
- [weekly-stripe-revenue](https://clickruntime.com/templates/weekly-stripe-revenue)
- [Scheduled tasks in ChatGPT and Claude](https://clickruntime.com/use-cases/scheduled-tasks-in-chatgpt)
- [Daily standup in Slack](https://clickruntime.com/use-cases/daily-standup-in-slack)
- [Slack channel summary](https://clickruntime.com/use-cases/summarise-slack-channel)
- [Assistant scheduled tasks alternative](https://clickruntime.com/alternatives/chatgpt-claude-scheduled-tasks)
- [Zapier alternative](https://clickruntime.com/alternatives/zapier)
- [Docs: connections-and-secrets](https://clickruntime.com/docs/connections-and-secrets)
- [Docs: asking](https://clickruntime.com/docs/asking)

## Extend it: what you can add next

The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.

- **Add yesterday's Stripe revenue to the morning post** (Any app or API)
  Prompt: "Add to my morning Slack post: yesterday's Stripe revenue and number of new customers."
- **Open with a two-line AI summary of what needs attention today** (Built-in AI)
  Prompt: "Change my morning Slack post so it starts with a two-line summary of what needs attention today, based on the bugs listed."
- **Show the change since yesterday next to each number** (Memory between runs)
  Prompt: "Change my morning Slack post so each number shows the change since yesterday, like 12 open bugs (+3)."
- **Skip public holidays and post a different message on Mondays** (Multi-step logic)
  Prompt: "Change my morning Slack post to skip German public holidays, and on Mondays include last week's closed bugs."
- **Add a Friday afternoon wrap-up post** (Schedules)
  Prompt: "Add to my morning Slack post: every Friday at 16:00, post a wrap-up with the bugs closed this week."
- **Post an extra message when a deploy finishes** (Trigger links)
  Prompt: "Add a trigger link to my Slack post automation that our CI calls after a deploy, and post the version and who deployed it to #team."

## Questions

### Can ChatGPT send a Slack message every morning?

Not on its own. With ClickRuntime connected, ChatGPT sets up an automation that posts to your Slack channel at the time you choose, every weekday, after the chat is closed.

### Can Claude post to Slack on a schedule?

Yes, through ClickRuntime. Claude writes the automation and turns it on; ClickRuntime runs it on its servers.

### How is this different from Slack's /remind?

/remind repeats a fixed text. A ClickRuntime automation fetches fresh data each time, such as open bugs, sales or calendar items, and can use AI to summarise it.

### Can it post as me rather than as an app?

Yes, if you connect your own Slack account in the ClickRuntime dashboard; the assistant then posts with that account.

### Which timezone does it use?

The one you give. If you don't say, the assistant asks before saving it.

### What can I add later?

Revenue numbers, an AI summary, changes since yesterday or a Friday wrap-up. See the Extend it list.
