Common recipes

Start from a few practical workflow recipes that are easy to build and easy to verify.

Slack alerting

A classic first workflow:

1. receive a webhook or app event
2. format the important details
3. send a Slack message

This is a good starter because the output is immediately visible.

Gmail triage

A strong inbox workflow pattern:

1. watch for new messages
2. use AI to summarize or classify them
3. route the result to the right system or person

This is useful when the team handles repeated inbound requests.

Notion updates

Use this recipe when the workflow should create or update internal knowledge:

1. collect the source input
2. transform or summarize it
3. create or update the matching Notion content

This is helpful for structured note capture and lightweight operational tracking.

Google Sheets logging

A very practical automation pattern:

1. trigger on a new event
2. map the important fields
3. insert a row into a spreadsheet

This is a great way to build audit trails, lead logs, or lightweight reporting.

Calendar-driven workflows

When timing matters, calendar-based workflows can help with:

• agenda generation
• reminders
• post-meeting summaries
• event-driven follow-up

These workflows are especially effective when combined with AI summarization or downstream notifications.

Why recipes are useful

Recipes give you a mental shortcut.

They help you recognize that many workflows are just variations of a few repeatable structures. Once you understand the structure, adapting it to a new business case becomes much easier.