Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Building Workflows 101

Workflows in BuddyBee let you automate multi-step tasks by linking instructions together. Each workflow runs step by step, following the guidance you set.

⚡ Tip: Keep each step simple. It’s easier to test and troubleshoot when BuddyBee only has to focus on one task at a time.

How the Agent Works

BuddyBee doesn’t interact with web pages the way you do. Instead of moving a mouse and clicking around, it sends commands directly to the browser. To make sense of a page, it looks at both the code that sits behind it and the screenshots it takes along the way.

The tricky part is that many websites are designed for looks, not structure. The code underneath can be messy or inconsistent, which makes it harder for BuddyBee to navigate. When that happens, adding some extra context to your instructions can really help the agent stay on track.

The good news is that BuddyBee keeps improving. As the libraries behind it are rewritten and refined, it’s getting much better at handling even complicated or poorly built pages.

Creating a Workflow

The easiest way to start is to map out your process in the Chat Dialogue. Break it into small, testable steps and run through them until everything works smoothly from start to finish.

When you’re ready, click Build My Workflow and fill in the basics:

  • Workflow Name: What you want to call it.
  • Description: A short summary of what it does.
  • Field Names: the information a user needs to provide (for example, a property address or contact name).

Next, add your first step. You can either create it from scratch or generate it from the conversation you’ve already had (recommended). When you do this, you’ll be asked to pick the part of the dialogue that matches the step you’re adding - so be as precise as you can.

What Goes Into a Step

Every step has a few fields to complete:

  • Instructions: The exact task(s) BuddyBee should perform.
  • Task Complexity: Usually best left on Auto. If you prefer, you can choose low, medium, or high reasoning. This determines the level of reasoning that will be activated on the model. Where reasoning is applied, the model will think through and come up with a plan for the task. Higher levels give BuddyBee more time to think, but also use more credits.
  • Inputs Required: The details a user must enter to trigger the workflow (for example, property address and parties to a lease).
  • Outputs Expected: What you want BuddyBee to produce (for example, a saved form link, or a seller’s contact details).
  • Read Prior Steps: Switched on by default. This lets BuddyBee use the results of earlier steps as context. Leave it on unless you have a reason not to.
  • Enabled: Keep this ticked to include the step in your workflow. If you untick it, the step will be skipped without being deleted. This is handy during testing — for example, if a step sends an email you don’t want to trigger until the workflow goes live.
  • Use Internet Browser: On by default. This tells BuddyBee to use a browser to complete the task. Switch it off if the step involves something else, like calling an API, sendingan email or querying the knowledge base. 

Testing & Troubleshooting

Workflows take a little experimenting to get right. If something doesn’t work the way you expected, just adjust the step instructions and try again. Keep refining until the workflow runs cleanly from beginning to end.

Remember, BuddyBee is interpreting both the structure and the look of the page. The clearer your instructions, the more reliable your workflow will be.

 Need help with anything else?

We are here to support you:

🌐 Knowledge Base

📧 Email: support@hutly.com