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.
Use a recipe to finish one piece of work and, if needed, bring it back later: 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.
Choose a starting point
- No tools to connect: Decide by Friday turns an unclear decision into something you can review.
- A mailbox or invoice list: Inbox triage and Chase overdue invoices start with work already waiting for you.
- A repeatable check: The morning readout and The pull request sweep show how to make the result repeat.
Start in one of your own chats, outside an organization, unless the guide says otherwise. An organization's chats can use a different set of connections.
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
Find what needs an answer from you and save replies as drafts to review.
Unstick pull requests waiting on review
Every week, the pull requests waiting on a review, in your own GitHub repositories.
GitHubStart 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 | No model runs 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 for connected apps or web for web search.
How schedules run has the exact rules: what a run can use, missed runs and failures.
A time without a supplied time zone falls back to UTC. Include the zone rather than relying on an earlier message. Name the zone by city: "9:00 Berlin time".
Set up a schedule with the form
Use the form when you want to choose the timing, delivery, and tools yourself. The full form walkthrough covers each field and gives copyable examples.
Once it is created, choose Run now on the schedule's page. Read the result and check its destination before leaving it to repeat. A reminder only posts saved text, so it cannot test whether June can read your source. If it fails, open Open history, fix the missing connection or instruction, and try again.
What June does not do
- These recipes ask for mail drafts. Review and send them in your mail app; Gmail also supports sending through June after approval of the specific mail.
- The form cannot edit a schedule; delete it and create it again, or ask June in a chat to change it.
Follow-ups
Ask June to check back at a time and act if nothing moved. Reminders, repeating schedules, the Schedules page, and what June does without asking.
Chase overdue invoices
June finds the overdue invoices in your sheet or mailbox, drafts a payment reminder mail for each, and brings the thread back on the day you set to check again.