Ready-made setups

Starting points for common jobs. Each one is a bot, a few apps and usually a routine. Create the bot, paste the job into its chat, and adjust the details to yours. For what makes these work, see Set up a bot that works.

Morning inbox brief

Apps: Gmail or Outlook. When: weekdays at 8:00.

You look after my inbox. Every weekday at 8am, read unread mail from the last 24 hours, label each as Client, Team, Supplier or Newsletter, and write draft replies to client mail that needs an answer. Don't send anything. Post a summary here: first what's urgent, then one line per thread with who, what and what you drafted.

Drafting doesn't send. To be sure nothing goes out unseen, use Ask me: every email then waits on a card with Send or Discard. See Approvals.

Meeting prep

Apps: Google Calendar or Outlook, and your email. When: weekdays at 7:30.

Every weekday at 7:30, look at today's meetings with people outside the company. For each one, write a short brief: who they are (search the web), our last emails with them, open questions, and what I should get out of the meeting. Skip internal meetings.

Weekly numbers page

Apps: where your numbers live, such as HubSpot, Stripe or a Google Sheet. When: Mondays.

Make a page with last week's new deals, revenue and churn compared with the week before, with a chart for each. Update it every Monday at 7am.

The bot publishes a page and keeps it fresh with a routine. Choose Share on the page to share it with your team's space.

Competitor watch

Apps: none; the bot uses the web. When: Mondays.

Every Monday, check the pricing and product pages of Competitor A, B and C (links below). Tell me only what changed since last week, with the link, and say "no changes" if nothing did.

To be told only when something changes, ask for a routine that checks every few hours and posts only on a change. See Routines.

Team knowledge bot

Where: a team space. Knowledge: a Google Drive folder of your handbook, policies or product docs.

You answer colleagues' questions about our policies and products. Answer only from the documents you've learned; name the document you used. If they don't cover it, say so and suggest who to ask. Never guess numbers or dates.

Then send it the folder's link to learn. Everyone in the space can ask it, and the documents answer through the Drive account of the person who added them, so pick a folder everyone may read. See Knowledge sources.

Help in a Slack channel

Apps: Slack, in Settings → Messaging. Where: one channel.

In #support-internal, answer questions about our tools and point people to the right doc. If someone reports an outage, tag @oncall and stop.

Add the bot to the channel, approve it under Requests, then open the conversation's Settings: choose Mentions only and put the rule above in Room guidance. In the room, the bot acts with your apps, so keep approvals on. See Chat apps.

Pull request review

Apps: GitHub. When: a pull request opens.

When a pull request opens in our repo, review it with the Interrogate skill and post the findings here, most serious first. Don't comment on GitHub.

In the routine, add a Git event trigger and add its URL to the repository as a webhook. Runs started this way ask before any action that changes something. See Routines.

Daily research digest

Apps: none, or Slack in Integrations to post it. When: every morning.

Every morning, find the three most important news items about electric ferries from the last day, with a two-sentence summary and the source link for each. Skip anything you reported before.

Once a digest looks right, say "save how you make this digest as a skill", so any bot can make one.