Buzz Workflows help you automate repeatable processes in Hive. By combining Workflows (triggers + conditions) with Buzz Tools (the actions Buzz can take in Hive and connected apps), you can create powerful end-to-end automations that save time and keep work consistent.
Workflows
Workflows are automations that run when something happens in Hive (or in a connected app). A workflow typically includes:
A trigger (what starts the workflow)
Optional conditions (rules that decide when it should run)
One or more steps, often including Give Buzz a job, where Buzz performs work based on your instructions
For more on Workflows, read here.
Buzz Tools
Buzz Tools are the set of actions Buzz can take on your behalf. Depending on what’s enabled in your workspace, tools can include:
Creating or updating actions
Updating action fields (status, due date, custom fields, labels, assignees)
Posting messages or notifications
Pulling data from connected apps (for example, Salesforce)
Drafting content (for example, summaries or email drafts)
Tip: When you are designing an automation and you are not sure if Buzz can do something, start by reviewing the available tools.
Personal vs workspace-level Buzz settings
Buzz can be configured at two levels:
Personal settings: preferences that apply to you (examples: personal connections, individual behavior preferences)
Workspace settings: shared instructions and rules that apply across the workspace (examples: writing style guidelines, formatting expectations, team-wide policies)
Workspace-level settings are especially helpful when multiple people will rely on the same workflows and you want consistent outcomes.
Thinking Mode
Thinking Mode is a higher-reasoning mode Buzz can use for more complex tasks, like interpreting unstructured intake, generating structured outputs, or performing multi-step transformations. It is designed for situations where you want more careful reasoning and higher quality results from Buzz in automations. You can toggle this on/off in your Buzz messaging window.
How to use Buzz Workflows
1) Enable Workflows
In your workspace:
Go to Apps
Enable Workflows
Confirm you have permission to create and manage workflows
2) Turn on & connect integrations
If you want to trigger workflows from a connected system or pull external data into Hive:
Go to Apps
Enable the integration (for example, Salesforce)
Connect your account
Once connected, Salesforce becomes available inside Workflows as:
A trigger (for example, when an opportunity is created or updated)
A data source Buzz can reference to populate action fields and context
Core automation patterns you can implement
Pattern A: Salesforce → Hive action creation (structured intake from CRM)
When to use: You want work created automatically when a CRM record changes, so teams can respond quickly and consistently. We will be using Salesforce as a example.
Trigger ideas:
Opportunity created
Opportunity updated (for example, stage changes)
Account updated
Typical outcome:
Create a new Hive action (or update an existing one)
Populate custom fields with CRM data
Assign the right owner, add labels, and set a due date
To make it easier for Buzz to understand, add specific steps to any complex or multi-layered prompt.
Example (plain text steps):
Trigger: Opportunity updated in Salesforce
Condition: Stage changes to “Negotiation”
Step: Create Hive action in “Customer Operations” project
Step: Populate fields (Account, Amount, Close Date, Owner)
Step: Assign to account owner and apply “Needs review” label
Pattern B: Forms → Projects → Automated routing and enrichment
When to use: You want standardized intake, so requests enter Hive consistently and route to the right place.
Trigger ideas:
Form submitted
Action created from a form submission
Typical outcome:
Normalize the action title based on form answers
Populate custom fields
Route to the correct project/section
Notify the right stakeholders
Example (plain text steps):
Trigger: Form submission creates a new action
Step: Buzz rewrites the title to a standard format
Step: Buzz fills custom fields from form answers
Step: Buzz assigns the action to the right owner based on request type
Step: Buzz adds labels and posts a comment confirming receipt
Pattern C: Automated title standardization (from description or form answers)
When to use: You want consistent naming for reporting, filtering, and handoffs. This is especially useful when intake text is long or inconsistent.
Trigger ideas:
Action created
Status changes (for example, when work moves from “Unstarted” to “In Progress”)
Typical outcome:
Buzz generates a clean, consistent title from structured inputs (like form fields) or unstructured text (like a description)
Pattern D: Mailbox assistance (draft replies, triage, and labeling)
When to use: Your team handles lots of repetitive communication and wants to speed up response workflows.
Trigger ideas:
New email received (where supported)
Manual workflow steps that create drafts from email content
Work created in Hive that requires a response
Typical outcome:
Draft replies for common questions
Summarize threads for internal handoff
Apply labels for triage and prioritization (for example, “Needs reply”, “Change request”, “Scheduling”)
Pattern E: Proofing and approvals (Buzz Proofing)
When to use: You want an extra review layer for documents to catch issues early and keep output consistent.
Trigger ideas:
Proofing step in a process (for example, before publishing)
Document uploaded to Proofing
Typical outcome:
Buzz flags spelling, grammar, clarity, and accessibility issues
Reviewers can filter by issue type and apply changes more efficiently
Teams get a consistent “first pass” review before human approval
For instructions on how to use Buzz directly in the Proofing & Approvals app, read more here.
Buzz Tools and Connections
Native integrations (recommended starting point)
Hive supports a range of built-in integrations. When a native integration exists, it’s usually the fastest way to:
Trigger workflows from external systems
Pull data into Hive actions
Keep automation maintenance low
Examples include Salesforce, Jira, GitHub, and others available in your workspace Apps list.
Custom connections (HTTP / MCP)
If you need to integrate with a system that is not available as a native app, you can set up a custom connection so Buzz can interact with it as a tool.
HTTP connections allow Buzz to call approved API endpoints you define
MCP connections can expose a tool server to Buzz where supported
Safety note: Only connect Buzz to endpoints that are approved by your organization, and follow your company’s security and compliance policies for external integrations.
Debugging and iteration (how to improve outcomes)
View runs
Most workflows provide a View runs experience so you can:
Confirm when the workflow executed
See what triggered it
Review what Buzz did step-by-step
Show thinking
When available, Show thinking helps you understand Buzz’s reasoning:
Why it chose a specific action
How it interpreted your instructions and inputs
Where it may have misunderstood or lacked context
Ask “why did you do that?”
A practical debugging loop:
Open a workflow run’s thread or context
Ask Buzz why it made a decision or took a step
Refine:
The workflow instructions (the Buzz job prompt)
Trigger conditions
Field mappings
Workspace-level Buzz settings (for consistent team-wide behavior)