Put a report on a schedule
Create a Routine so your Talent runs the same work every week and sends the result to Slack, Telegram, iMessage, or your TalentOS home.
A Routine is work your Talent runs without being asked. You write the instructions once, pick when it runs and where the result lands, and it keeps running. Nobody has to remember Monday morning.
This page walks one real example end to end: a Monday 09:00 pipeline summary built from HubSpot and delivered to a Slack channel.
A worked example
-
Open Routines in the Workspace group of the left navigation.
-
Click New routine, then Set up manually. (The other option, Create with Talent, is covered below.)
-
Name it something a teammate would recognise:
Monday pipeline summary. -
Category groups it on the Routines page. Pick the one that fits.
-
Instructions is the whole brief. Write it the way you would brief a person:
Pull every open HubSpot deal closing in the next 30 days. Group them by stage. Give me total value per stage, then list any deal that has not moved in 14 days. Keep it under 200 words.
-
Under When, choose Weekly, click the day chips to select Monday, set the time to 09:00, and confirm the time zone. The schedule reads back as a sentence: Every Monday at 9:00 AM. Check that sentence before you continue.
-
Under Result delivery, tick Slack and choose the channel. Delivery is where the finished result is sent, and you can pick more than one place.
-
Click Create.
You land on the Routine's detail page. It shows what your Talent will do, the schedule, the connections the work needs, and its run history.
Or just ask
You do not have to use the form. In web chat, Slack, or Telegram, tell your Talent what you want:
Every Monday at 9am, summarise our HubSpot pipeline and post it to #revenue.
Your Talent creates the Routine and reads the schedule back to you. If you leave something out that matters, it asks a short follow up question rather than refusing. See Choose a cadence and where results land.
A Routine runs with your connected tools and your permissions. The HubSpot data in the example is the data your own HubSpot connection can see. If you have not connected HubSpot yet, connect it before the first run.
Change it later
Open the Routine and use Edit routine to change the name, instructions, schedule, or delivery. Pause Routine stops future runs and keeps everything else intact. Resume Routine starts it again from the next scheduled slot.
What to check
- The badge says "Needs attention". Something stopped it, most often a connection that expired. Open the Routine and read the message on the card, then see Fix a Routine that is not running.
- Nothing arrived in Slack. Check Result delivery on the Routine. If no delivery target is ticked, the run still happens and the result is saved to the Routine's history, but nothing is pushed to you.
- The schedule sentence is wrong. The sentence under When is what actually gets stored. If it does not match what you meant, fix it there rather than in the instructions.
- The result is thin or off target. The instructions are the brief. Say what to include, what to leave out, and how long it should be, then run it once from the Routine page to check.
Related
Choose a cadence and where results land
Once, hourly, daily, weekly, time zones, and the four delivery targets.
Run history and Routine states
Active, Paused, Needs attention, Held, Completed, and where to read what happened.
Save a Skill you can reuse
Turn work that keeps coming back into a package your Routine can pin.
Know who can see your chats and memory
Your conversations, memory, runs, and connections are yours alone. Here is exactly what an admin can and cannot see, and why.
Choose a cadence and where results land
The four Routine cadences, how time zones and end dates work, and how to send a result to Slack, Telegram, iMessage, or TalentOS.