Use Buzz to write the email
In a workflow, you can send an email whose body is Buzz’s reply from the step before it. Tell Give Buzz a job what to write, then turn on Use Buzz output from previous step in Send an email.
Set up the two steps
Open the Workflows app and create or edit a workflow.
Add a Then operation: Give Buzz a job.
In What should Buzz do?, describe the email Buzz must write. Select Create AI workflow.
Add a new step immediately after that Buzz step.
In that next step, add Send an email.
Add recipients and a subject. You can still use tokens such as Created by or Assignee in the subject and address fields.
Turn on Use Buzz output from previous step. The body editor is replaced with: Buzz’s response from the previous step will be the email body.
Optionally turn on Link action in email or Send individual email to each recipient.
Save and enable the workflow.
The checkbox is available only when the step before has exactly one Buzz step and no other operation. If the checkbox is disabled, Hive shows: Add exactly one Buzz job to the immediately preceding step.
Example workflows
Client recap on complete — Trigger: Status changes to Completed. Step 1: Give Buzz a job to write a short recap of the action. Step 2: Send an email to the created-by person, with Use Buzz output from previous step on.
Form confirmation — Trigger: Form is submitted. Step 1: Give Buzz a job to draft a confirmation from the form answers. Step 2: Send an email to the submitter using Buzz’s reply as the body.
Availability and limitations
Create a summary and Deadline digest steps do not fill the email body.
Put Send an email in the next step, not in the same step as the Buzz job. An empty step or a skipped step between them clears Buzz’s reply, and the email fails.
The previous step must produce exactly one non-empty Buzz reply. Zero replies or more than one reply fails the email with: SendEmail requires one non-empty Buzz response from the immediately preceding workflow step.
You still need recipients and a subject. Send an email requires a paid plan.
When Buzz writes the body, action tokens in the body are not applied. Tokens in the subject and recipient fields still work when the workflow has an action.