Buzz Snippets are reusable automations in your Hive workspace. Each snippet is a saved, versioned script Buzz can run on demand — from chat, from the Snippets settings page, or from an App Workflow.
Use snippets when you need the same multi-step logic to run reliably, with structured input and output, again and again.
What is a Buzz Snippet?
A Buzz Snippet is a workspace automation that:
Runs deterministic JavaScript (same inputs → same logic path)
Accepts structured input and returns structured output (JSON schemas)
Can call Hive tools (update actions, send messages, look up projects, etc.)
Can connect to external APIs (HTTP connections) and MCP servers
Can remember state across runs using snippet memory
Has a draft → publish lifecycle so you can test before going live
When should I use a snippet?
Good fits
Repeatable workspace automation you want to rerun from chat or wire to a workflow
Multi-step logic with branching, validation, or several Hive tool calls
Integrations with external systems via HTTP or MCP
Automations that need to remember state between runs
Anything you’d describe as a “macro,” “script,” or “reusable automation”
Usually not needed
One-off tasks (“update this action”)
Simple scheduled summaries (App Workflow + Buzz prompt is often enough)
One-time file exports
Open-ended research
Rule of thumb: If Buzz would need the same long chain of tool calls every time, a snippet is probably the better answer.
How to create a snippet
Most snippets are created in Buzz chat, not by writing code manually.
Open Buzz.
Describe what you want automated. Be specific about:
What should happen
What inputs the snippet needs (e.g. action IDs, project ID, date range)
What it should return
Any external systems involved
Ask Buzz to create a Buzz snippet for that workflow.
Buzz will:
Write the snippet code
Define input/output schemas
Dry-run it with sample data
Publish it once the dry run succeeds
Example prompts
“Create a Buzz snippet that finds all overdue actions in project X and posts a summary to our team group.”
“Build a snippet that calls our external CRM API and creates a Hive action from the response.”
“Make a reusable snippet that assigns unassigned actions in a project to the project owner.”
New snippets are private by default. You can give specific people editor access or make the published version available to everyone in your workspace. These are separate settings, explained under Sharing below.
How to run a snippet
When you run a snippet from Buzz chat or the Snippets settings page, it uses your permissions. Access to a snippet does not automatically give you access to the Hive data or external connections it uses.
Option 1: Ask Buzz in chat
Open Buzz and say something like:
“Run the [snippet name] snippet with action ID abc123.”
“Use my overdue-actions snippet for project XYZ.”
Buzz looks up the published snippet, builds input from the schema, runs it, and summarizes the result.
Option 2: Insert from the Tools menu in Buzz
Open Buzz.
Type
/to open the command menu.Choose Tools → Buzz snippets.
Select Run snippet: [name].
Send the message. Buzz runs the snippet using the published version.
Only published snippets appear in this menu.
Option 3: Run from an App Workflow
Add a Run a snippet step to an App Workflow so the snippet runs automatically when the workflow trigger fires (e.g. action completed, schedule, form submitted).
Open App Workflows.
Create or edit a workflow.
Add an operation: Run a snippet.
Select a published snippet.
Save and enable the workflow.
The workflow passes trigger data into the snippet as input.
Manage snippets in settings
Path: Profile menu (avatar) → My settings → Buzz AI → Snippets
The options available depend on your access to each snippet. You can:
View snippets you own, snippets shared with you as an editor, and published snippets made available to your workspace.
Inspect the published version’s flow diagram, input/output schemas, and allowed tools.
Run a published snippet with JSON input.
If you own the snippet or have editor access, you can also view drafts and older versions, dry-run changes, publish or disable the snippet, manage sharing, and delete it.
Inspect the steps inside a Core flow node
Use Core flow for an overview of a snippet. Where detailed steps are available, you can expand a node to inspect that part of the Advanced flow without leaving the overview.
Open a snippet in My settings → Buzz AI → Snippets and select the version you want to inspect.
Choose Core flow.
On a node with a Show detailed steps control, click the control or the collapsed node to expand it.
Select Hide detailed steps to collapse it. Opening another node closes the one you were viewing.
Not every node or version has detailed steps available. You can also switch to Advanced flow to view the full detailed chart when one is available. Expanding a node only changes the view; it does not edit or run the snippet.
Test a snippet
Select a snippet. If you have editor access, select the version you want to test.
Switch to Advanced flow, expand Advanced, and open the Input tab.
Enter a JSON object matching the snippet’s input schema. You can also use Add Buzz generated test input when available.
Choose the appropriate run option:
Dry run — available to the snippet owner and editors. For a published version, leave Live run off to dry-run it.
Run published version — runs the published automation. Editors can turn on Live run to select this option; members with workspace access only see the published run option.
Running the published version can make the changes defined by the snippet, such as updating actions or sending messages. Review the input before running it.
After a dry run, review the result, logs, and any errors before publishing changes. Workspace access alone does not allow dry runs or access to drafts.
Sharing
You can make a snippet available for your workspace to use and separately choose who can edit it. Open the snippet in Snippets settings to manage these options.
Let your workspace view and run a snippet
Turn on Available to everyone in this workspace to let workspace members find, view, and run the snippet’s current published version using their own permissions.
This setting does not grant editor access. Members who only have workspace access cannot view drafts or older versions, dry-run changes, publish, disable, delete, or change sharing. They can see their own run results, but not other people’s run history.
The snippet must have a published version before it becomes available to other workspace members through this setting.
Choose who can edit
Under Editors, choose:
Setting | What it allows |
Only creator | Keeps editing limited to the snippet owner. |
Specific people | Gives the selected people editor access alongside the owner. |
Editors can run published versions, edit drafts, dry-run changes, publish, disable or delete the snippet, and change who has access. Choose collaborators who should be able to manage the automation.
To add or change editors, select Specific people, choose the people, and close the people picker. Review the Update snippet access? dialog, then click Update access to save.
Removing someone’s access may stop workflows they own that depend on the snippet. If Available to everyone in this workspace remains on, removing someone as an editor still leaves them able to view and run the published version as a workspace member.
Shared snippet memory
Snippet memory is shared across runs of the same snippet. It is not a separate memory for each person who runs it. Information saved by one run can be used by later runs, including runs started by other people.
Delete a snippet
To delete the entire snippet, you must own it or have editor access. To remove only its unpublished changes, use the Delete a draft version instructions below.
Select one or more snippets (checkbox).
Click Delete.
Deleted snippets disappear from settings and from the Buzz Tools menu.
Drafts, versions, and publishing
Every snippet has versions:
Status | Meaning |
Draft | Work in progress. The owner and editors can view and dry-run it. Workspace access alone does not give access to drafts. |
Published | Live version. Runnable from chat, Tools menu, and workflows. |
Disabled | Previously published version turned off. |
Typical flow
Buzz creates a draft.
Buzz dry-runs with realistic input.
After a successful dry run, Buzz publishes.
Further edits create a new draft version; publish again when ready.
If you own the snippet or have editor access, ask Buzz: “Update the [snippet name] snippet to also …” Buzz edits the draft, dry-runs, and republishes when ready.
Delete a draft version
You can permanently delete a snippet’s latest draft from its version history. You must be the snippet’s original creator and still have access to it. Editor access alone does not allow you to delete an individual draft version.
Open My settings → Buzz AI → Snippets and select the snippet.
In Versions, find the latest version marked Draft.
Hover over that version’s row and click the trash icon, labelled Delete draft version followed by the version number.
Review the Delete draft version? confirmation, then select Delete.
If a published version exists: Only the draft is deleted. The published version is not changed, and it becomes the selected version.
If there is no published version: Deleting the draft also removes the snippet. The confirmation warns you before you proceed.
This control is available only for the latest draft. It does not delete published versions or older versions.
External connections (HTTP & MCP)
Snippets that call outside Hive need connections configured first.
Path: My settings → Buzz AI → Connections
HTTP connections — REST APIs (header auth or OAuth)
MCP servers — Model Context Protocol tools
When Buzz builds a snippet that uses an external service, it binds those connections into the snippet. If OAuth is required, the connection owner may need to complete OAuth in Connections before the snippet can run.
Snippets vs slash commands vs workflows
Buzz Snippet | Slash command | App Workflow + Buzz prompt | |
What it is | Versioned code automation | Saved Buzz instructions | Trigger + AI step |
Best for | Deterministic, repeatable logic | Quick reusable prompts | Scheduled/event-driven AI tasks |
External APIs | Yes (HTTP/MCP) | Via Buzz tools inline | Via Buzz tools inline |
Strict input/output | Yes (JSON schemas) | No | No |
Runs in workflow | Yes (Run a snippet) | No | Yes (Buzz step) |
Quick reference
Here's the breakdown of where, when and how to use snippets:
Task | How |
Create snippet | Ask Buzz in chat |
Run snippet | Ask Buzz, or |
View/manage | My settings → Buzz AI → Snippets |
Set up APIs | My settings → Buzz AI → Connections |
Automate on trigger | App Workflow → Run a snippet |
Share with team | Snippets settings → Available to everyone in this workspace for published access; Editors for editing access (owner or editor required) |
Need help building a specific automation? Open Buzz, describe the workflow end to end, and ask Buzz to create and publish a snippet for you.