Recipes

Step-by-step follow-ups you can set up today: chase overdue invoices, answer waiting mail, unstick pull requests, start the day, decide by Friday.

A recipe is one real follow-up, set up end to end: what you need, what to type, and where June stops. Pick the one closest to what's stuck for you and swap in your own names.

Your own chats are the ones outside an organization; an organization's chats reach less of your tools.

Chase overdue invoices

Find what is overdue, get a reminder mail drafted for each, and a check-back on the date you set.

Answer the mail that waits on you

What needs an answer from you, with replies drafted. June never sends.

Unstick pull requests waiting on review

Every week, the pull requests waiting on a review, in your own GitHub repositories.

Start the day with what needs you

A schedule that reads your mail and calendar at seven and posts what needs you.

Decide by Friday

The decision you keep postponing: a first draft now, and the thread back on the day.

Two ways June comes back

Happy to reply when it comes back? Ask in chat for a reminder. Want the check done while you're away? Use a schedule: from the form, or ask June and name its toolsets.

	A reminder from chat	A schedule
Set it up	Ask in any thread, in plain words	New schedule on the Schedules page, or ask June in a thread
At its time	Posts your words in the thread and notifies your devices	Runs your instruction on its own
Reads your tools	When you reply in the thread	Only the toolsets you list under Enabled toolsets or name to June
Posts to	The thread you asked in, or Slack	The thread you asked in, Slack, your newest own chat, your devices, or the schedule's own page
Paid	Nothing at its time; your reply is paid like any chat	Each run is paid like one reply

A schedule June sets up for you from chat runs without your tools unless you name them, such as integrations and web from the table below.

How schedules run has the exact rules: what a run can use, missed runs and failures.

June is not told your time zone, so a time without one, such as "at 9", is read in UTC. Name the zone by city: "9:00 Berlin time".

Set up a schedule with the form

On the Schedules page, choose New schedule and give it a Name.

In Execution body, write the whole instruction. The run sees only this text and what June remembers, not the thread you discussed it in, so name the repositories, senders and files.

Under Delivery, leave local to keep the result under Open history on the schedule, or enter slack for a direct message from June in Slack (you need to have messaged June there once), web for your newest own chat, web: and a chat's id (the last part of its address) for that chat, or push for a notification on your devices. Several are separated by commas.

In Expression, enter the time as five fields: minute, hour, day of month, month, weekday. 0 7 * * 1-5 is 7:00 Monday to Friday, 0 9 * * 1 is 9:00 every Monday. Put your zone in Timezone, such as Europe/Berlin.

Under Enabled toolsets, list what the run may use, separated by commas. Left blank, the run has no tools.

Choose Create schedule. The schedule's own page opens; choose Run now there to try it.

Enter	So the run can
`integrations`	read and draft in the tools on your Integrations page: your mailbox, Microsoft 365, Notion and the others there
`web`	search the web
`documents`	read Google Docs, Slides, PDFs and images in your Google Drive from a link; plain text files there come through `integrations`
`terminal`	work in June's sandbox, including GitHub through the command line

Copy them exactly: the form refuses a name June does not know, such as an app's own name instead of integrations. The other fields can stay as they are.

What June does not do

It never sends mail in any recipe. It saves drafts; you send them.
The form cannot edit a schedule; delete it and create it again, or ask June in a chat to change it.