Skip to main content

Using Buzz Snippets

Learn how to automate your workflow with snippets.

Written by Michaela Rollings

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.

  1. Open Buzz.

  2. 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

  3. Ask Buzz to create a Buzz snippet for that workflow.

  4. 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.”

Snippets are private by default (only you can use them). Buzz can set sharing when you ask, or you can change it in settings (see below).


How to run a snippet

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

  1. Open Buzz.

  2. Type / to open the command menu.

  3. Choose ToolsBuzz snippets.

  4. Select Run snippet: [name].

  5. 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).

  1. Open App Workflows.

  2. Create or edit a workflow.

  3. Add an operation: Run a snippet.

  4. Select a published snippet.

  5. Save and enable the workflow.

The workflow passes trigger data into the snippet as input.


Manage snippets in settings

Path: Profile menu (avatar) → My settingsBuzz AISnippets

On this page you can:

  • View all snippets in the workspace you can access

  • See Published vs Draft status

  • Inspect versions, flow diagram, input/output schemas, and allowed tools

  • Test a snippet with JSON input

  • Change sharing (if you created the snippet)

  • Delete snippets you no longer need

Test a snippet

  1. Select a snippet.

  2. Open the Test input tab.

  3. Enter JSON matching the snippet’s input schema.

  4. Click:

    • Run published version — for published versions

    • Dry-run draft — for unpublished drafts

Review the test result, logs, and any errors before publishing changes.

Sharing

Snippet creators can set:

Setting

Who can use it

Only me

Creator only (default)

Specific people

Selected workspace members

Everyone in workspace

All workspace members

Shared users can run published snippets. Only the creator can edit sharing, publish, or disable.

Delete a snippet

  1. Select one or more snippets (checkbox).

  2. 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. Creator can dry-run; others generally cannot run it in production.

Published

Live version. Runnable from chat, Tools menu, and workflows.

Disabled

Previously published version turned off.

Typical flow

  1. Buzz creates a draft.

  2. Buzz dry-runs with realistic input.

  3. After a successful dry run, Buzz publishes.

  4. Further edits create a new draft version; publish again when ready.

To change a snippet, ask Buzz: “Update my [snippet name] snippet to also …” Buzz edits the draft, dry-runs, and republishes when ready.


External connections (HTTP & MCP)

Snippets that call outside Hive need connections configured first.

Path: My settings → Buzz AIConnections

  • 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 / → Tools → Buzz snippets

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 → Sharing (creator only)


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.

Did this answer your question?