Daily or weekly
Post a scheduled reminder in Teams
Your channel gets the same reminder at the same time, without anyone having to remember to post it.
- Runs
- Daily or weekly
- Apps
- Microsoft Teams
- AI
- Not needed
- Access
- write (ChannelMessage.Send)
Send this to your assistant
Create a ClickRuntime automation: every weekday at 9am, post 'Please update your pending tickets before standup' to our Support channel in Teams.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Every team has messages that should go out at the same time each week and are forgotten about whenever the person responsible is busy. The Friday reminder to submit timesheets, the Monday post listing this week's priorities, the daily reminder that the build freeze starts at 3 p.m. Each one depends on a single person remembering, and when that person is sick or on holiday, the reminder does not appear and a deadline is missed.
At the days and times you pick, ClickRuntime builds the message text and posts it into the Microsoft Teams channel you chose. The text can be fixed wording, or it can include the date or other details that change each time. Nobody has to open Teams to send it.
Team leads, office managers and project coordinators use it for reminders, daily status lines and recurring announcements.
What you get out of it
Deadlines are met more often
A timesheet reminder that appears every Friday at 2 p.m. gets more people to submit on time than one that depends on a manager remembering. Fewer late submissions mean less chasing and fewer payroll corrections.
Reminders no longer depend on one person
When the usual sender is on leave, the message still goes out at its usual time. A process that relies on someone's memory is fragile, and a schedule removes that single point of failure.
Consistent wording builds a habit
A message posted at the same time with the same format teaches the team to expect it. People start looking for the Monday priorities post, so it gets read instead of ignored.
Time zones are handled once
You set the delivery time once, so a distributed team gets the post at a sensible hour. Nobody has to send it from their own evening or early morning. That suits managers coordinating people across several offices.
Posts can carry the date or changing details
A daily status line can include today's date, a sprint day count or a link that is different each week. That keeps repeated messages useful, instead of reading like the same notice.
A tidy record in the channel
Scrolling back through the channel shows when each reminder or announcement went out. That is helpful when someone claims they never heard about a deadline. It also settles disputes quickly.
How it works
What happens, step by step
At the time you choose, every day or every week, ClickRuntime wakes up and runs.
It uses the message you wrote, for example: "Please update your pending tickets before standup."
The message is posted to your Microsoft Teams channel, such as Support, so nobody has to remember to send it.
Before it runs live
- Connect Microsoft Teams
What you get
Build your own
Need it to work differently?
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 Slack
- Combine it with other Microsoft Teams steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http
GRAPH = "https://graph.microsoft.com/v1.0"
TEAM_ID, CHANNEL_ID = "your-team-id", "19:support-channel-id@thread.tacv2"
@on_trigger
def run(event):
token = credentials.connection("microsoft", "work")
resp = http.post(f"{GRAPH}/teams/{TEAM_ID}/channels/{CHANNEL_ID}/messages",
headers={"Authorization": f"Bearer {token}"},
json={"body": {"content": "Please update your pending tickets before standup"}})
resp.raise_for_status()
return {"message_id": resp.json()["id"]}FAQ
Common questions
Can I post to more than one channel?
What if the message needs to change every week?
Does the message appear as coming from a person?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Keep a live status message in a Teams channel
One message in your channel always shows the latest status, instead of a new post every hour.
See how it worksGet a monthly list of inactive Teams guests
Each month you see the guest accounts that haven't signed in for 90 days, so you can remove them.
See how it worksGet a weekly summary of a Teams channel
Each Friday you get a short report of what each person discussed in the channel that week.
See how it worksKeep exploring
Set up “Post a scheduled reminder in Teams” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.