Contributing recipes

---
title: Outcome-first recipe title
description: One sentence explaining the finished system and why it matters.
icon: lucide-icon-name
contributor: Name or team
contributor_url: https://example.com/contributor
contributor_company: Company
contributor_company_url: https://example.com/company
---

## Overview

<!-- Explain the recurring problem and the outcome this recipe creates. -->

Overview paragraph.

- **Trigger**: Trigger type
- **Setup time**: About N minutes
- **Requires**: Product access, integrations, permissions
- **Serves**: Teams or roles
- **Cooked By**: [Name or team](https://example.com/contributor) from [Company](https://example.com/company)

## Ingredients

<!-- List product features, integrations, permissions, environments, and channels. -->

- Ingredient

## Steps

<!-- Use exact labels and Settings paths from the current product. -->

1. First step.

## Paste-ready configuration

<!-- Name the exact field for every paste block. Never include real credentials. -->

```text
Configuration or prompt
```

## Variations

<!-- Offer useful adaptations without turning them into separate recipes. -->

- Variation

<!-- State provider support, permission boundaries, and other limitations plainly. -->

**Pairs well with:** [Related recipe](/cookbook/example)