Easybeam
  • Getting Started
    • 👋What is Easybeam?
    • 📙SDKs
  • Features
    • 📝Prompts
    • ⭐Reviews & Score
    • 🧠Agents
      • Getting Started
      • Core concepts
      • Data Types
      • Sidebar
      • Start Step
      • Prompt Step
      • Decision Step
      • Action Step
      • Website Step
      • Database Step
      • Async Branch
      • Knowledge Step
      • API Step
      • Solo Agent
    • 📖Knowledge
      • Websites
      • Documents
    • 📋Logs
    • 🔍Analytics & Reviews
    • 🧑‍🔬Test Center
  • 🤖Documentation Agent
Powered by GitBook
On this page
  1. Features
  2. Agents

Action Step

Empower you Agents to take Actions

PreviousDecision StepNextWebsite Step

Last updated 1 month ago

Action steps are how you empower you AI Agents to take actions when certain conditions are met.

An Action step can have multiple different actions which will be assessed and then taken if criteria are met. If an Action is taken, the data from its last step will be the output for the action step, and can be referenced in the main branch by reference the output from the Action step.

IMPORTANT!

  1. If an action is triggered, then the LAST STEP of the action will be returned as the output.

  2. IF no actions are taken then the output of the Action Step is EMPTY.

Action Step

In each Action Step you can define,

  1. The name of the step (i.e. Journal Actions).

  2. The AI provider used to power this step.

  3. The Actions available to this step.

Actions

In each Action you can define,

  1. The name of the Action (i.e. Update Journal).

  2. The condition of the Action.

    1. This text determines when the action should be called (i.e. "A user has specified an edit to their journal").

  3. The sensitivity of the Action (defaults to 80).

  4. The Conversational Data required for this Action to be taken

Conversational Data

Conversational Data is data that's processed from the messages exchanged between the AI and the User. Each piece of Conversational Data is make of up a

  1. Name

    1. This is used to reference the data later on in the Action branch.

  2. Description

    1. This is used to know how to extract the data from the conversation. A good description is required to ensure smooth functioning.

Conversational Data Examples

  1. Name: Location, Description: The location the user has given in the conversation

  2. Name: Mood, Description: The mood or current emotion the user has described in the conversation

🧠