PulseRecipes (saved instructions)
How to build and share saved instructions you can run again and again.
A recipe saves the instructions you type into chat every time. Work with a fixed output — formatting minutes, copying into a daily report, filling in an interview scorecard — becomes a matter of picking a name. This article covers calling up recipes, creating them, and sharing and editing them. How to word the instructions themselves, with examples you can use as-is, is covered in Writing effective recipes.
Recipes are called from chat, and chat is available in the desktop app (macOS / Windows). How chat's scope is decided is covered in Asking your notes questions (chat).
What recipes suit
They suit work that produces the same shape of output repeatedly. For example:
- formatting minutes for internal circulation, or a daily report for your manager
- pulling just the take-aways and decisions out of recent meetings
- summarising trends in requests across meetings with several customers
- building a list of things to verify, or of defects, from development meetings
- drafting an internal procedure from support enquiry records
Calling up a recipe
Type a forward slash / in the chat input field and the available recipes are listed — those provided out of the box, those you have made, and those shared by members of the same workspace. Keep typing part of a name to narrow it down.
Opening the recipes tab from the sidebar menu shows the whole list at once.
Recipe names and short descriptions listed vertically above the input field, selectable with the arrow keys.
Finding recipes
The recipes tab is divided into sections.
- Recommended: recipes provided by Pulse together with ones contributed by users. A good starting point when you want ideas for how to analyse something.
- My recipes: the ones you have made.
- Workspace recipes: ones published by members of the same workspace.
The search field searches the body of the instructions as well as the recipe name. Search by the words of the situation you have in mind — “daily report”, “assessment”, and so on.
Creating a recipe
Open the creation screen
Type
/in the chat input field, or open the recipes tab from the sidebar and choose “Create recipe”.Give it a name
This name is the shortcut you use to call it from chat. Choose something that makes its purpose clear, such as “Minutes (internal circulation)”.
Write the instructions
The more specifically you say what to extract and what format to produce, the more consistent the result. How to decide the structure, Japanese-specific choices (polite or plain form, orthography, number formatting), and examples you can save and use as-is are in Writing effective recipes.
Choose where it is used
Choosing “a single meeting” makes it appear in chat on an individual meeting, usable both during and after it. Choosing “several meetings” makes it appear on the home screen, in folders, in person and company records, and when several meetings are selected — and not in chat on an individual meeting. A recipe can only be one or the other. To use the same instructions in both situations, create them as two separate recipes.
Specify an AI model (optional)
Under advanced settings you can specify which AI model runs the recipe. What you can specify depends on your plan. How to choose, and which plans this applies to, are in Choosing an AI model. Left unspecified, it runs on automatic selection.
Save it and set its visibility
A saved recipe can be kept to yourself, published to your workspace, or shared by link. Choosing the scope is covered in the next section.
- the name alone makes clear which situation the recipe is for
- you chose whichever of “a single meeting” and “several meetings” matches the screen you want to use it on
- the instructions specify the output's headings, number of items and tone
Sharing scope
A recipe's visibility has three levels.
| Setting | Who can see it |
|---|---|
| Private | only the person who created it |
| Within the workspace | members of the same workspace |
| Anyone with the link | everyone who receives the link |
Someone who receives a shared recipe can run it against their own notes, save it as their own, or make an edited version for themselves. They cannot change the author's version. Sharing a recipe also never exposes your meeting notes or transcripts to them.
Recipe instructions often contain things you would not want to leave your company — company and product names, team structures, assessment criteria, commercial terms. Choosing “anyone with the link” means everyone who receives that link can read the instructions in full. Write any recipe that might go to someone outside your company without internal specifics in it.
Building on someone else's recipe (remix)
Recipes made by other people show a “Remix” button. This makes a copy you can edit. It does not appear on your own recipes, since you can edit those directly.
A remix lets you change the settings as well as the instructions. If a shared recipe is set for “several meetings” and you want it on an individual meeting, remix it and switch it to “a single meeting”. The original is unaffected.
Editing and deleting
To edit
- Open the recipe from My recipes.
- Choose the pencil icon on the detail screen to enter edit mode.
- Make your changes.
- Choose “Save”.
To delete
- Open the recipe from My recipes.
- Choose the pencil icon to enter edit mode.
- Choose the bin icon at the bottom left.
Instructions cannot use variables
Recipes are static templates. Variables, merge fields and substituting values at run time are not supported. The instructions you saved are sent exactly as they are, every time.
To vary the conditions by project or by role, create separate recipes with the conditions written in. If, say, sales and engineering interviews have different assessment criteria, set up “Interview scorecard (sales)” and “Interview scorecard (engineering)” as two recipes.
If something is not working
The recipe does not appear in the list
Check whether it is set to “a single meeting” or “several meetings”. It does not appear in situations other than its setting. To change the setting of a shared recipe, remix it first and then switch.
The output comes out differently every time
Short instructions do not pin the format down. State the order of headings, the tone, the length per item and the table columns explicitly in the instructions. How to word them is explained in Writing effective recipes.
Output contains things that were not said in the meeting
Only the meeting data and attached material can be consulted. Asking for anything beyond that can lead to content being filled in. Put a rule in your instructions saying “do not write anything that is not in the record”.
I want to stop a shared recipe being visible outside the company
Change the visibility setting. Note, though, that copies already remixed remain with the people who made them. Rewrite instructions containing anything sensitive before sharing.