Integrations and scheduled missions

Connect outside services the assistant can use (Google, YouTube, Slack, GitHub and Notion), and create tasks that run at a set time just by saying something like "Every Monday at 9…". Scheduled tasks post to the chat only when something has changed since last time. For schedules made from a skill (missions), you manage running now, pausing, run history and which agent runs them.

In Chapter 10, you saved the quote check method as the quote-check skill. A skill runs only when you call it. In this chapter, you first connect outside services the assistant can use, and then make work run on its own at a set time.

Connections — outside services the assistant can use#

In Settings (the circle with your name at the top right) › Accounts, Connections has five services. Each card lists the tools the assistant gets to use.

This chapter uses examples that don't need personal account connections. Examples that use Google and Slack connections (putting events from new YouTube videos on the calendar, a weekly Slack summary) are in the integrations, skills and missions video.

Try it 1 — schedule it by saying so#

You want to keep track every week of the time left and the to-dos until Moonlight Coffee Store #2 opens. Type in chat:

Every Monday at 9 AM, tell me in three lines how many weeks are left until Moonlight Coffee Store #2 opens (March 2, 2027) and what to take care of this week.

When your message has words like "every, daily, weekly, monthly, on a schedule, recurring", the assistant doesn't do it right away and takes it as a schedule. A schedule chip is attached below the answer.

Check: The task name and next run time on the chip. The assistant names the task and writes the instruction it will run each time on its own (in our run: "I'll set a Monday 9 AM reminder that counts down the weeks to the March 2, 2027 opening and flags what to focus on that week.").

See the list and details in Settings › Scheduled tasks.

Quiet when nothing has changed#

Each time a scheduled task runs, it runs with the condition "if nothing differs from what the last run shared, answer only 'No change'", and if the answer is "No change", nothing is left in the chat (not even a divider). If the previous run is still going, that run is skipped. This keeps the same content from piling up every day and making you miss the alerts that matter. Runs that passed quietly still show as No change under Previous runs on the details screen.

Try it 2 — schedule a skill (mission)#

When you run a skill from Chapter 10 at a set time, it becomes a mission. Missions have more to manage than ordinary schedules.

Open quote-check in Settings › Skills, and below it there are schedule buttons (Every morning at 8 · Twice a day (12:00, 21:00) · Hourly during weekday market hours · Every Monday at 9). Choose Every Monday at 9, write the quote to check in the Input values (JSON) box (write it as {"name": "value"}, like the example in the box), and click Schedule Every Monday at 9. You can also choose the schedule when you save from the skill draft card.

When you open the mission in Settings › Scheduled tasks, it has more items than an ordinary schedule. Click Run now to try it right away.

A mission decides "whether anything changed" from a result line like the one below that the skill leaves on the last line of its answer. Every time the mission runs, it tells the assistant to leave this line. If there's no result line, a run that ended normally is still recorded as Completed, but since it can't tell whether anything changed, it's marked Unknown if changed and the notification is sent. It's Failed only when it ended with an error or gave no answer at all. In the shot above, both runs left a result line: the Deep Agents run checked the quote ("all 8 pre-send items passed …", Changed), and the Claude Code run found the skill but not the input file (No change, see the note below).

MISSION_RESULT: {"changed": true, "summary": "2 need checking — typo in the validity wording, stored value is the old total"}

The status switch, Run now and Previous runs are the same as for ordinary schedules. Missions also have the following.

Mission results go only to the person who set it up. That's because a skill is one person's work done by one agent. For work that several people do in turn (review, approval), you schedule a process instead of a mission. Say something like Start the SNS trend response process every Monday at 9, and a new process starts each time it runs, passing to the assignee at each step (you make processes in Chapter 17).

Next#

A scheduled mission reports its results to just you. In the next chapter, you'll see panel apps, small tables the team views and edits together, like a quote tracker, made with a single request (Chapter 12).