Workflows
Power your communications with AI workflows
The HappyRobot Platform is your home for building, deploying, and managing your voice AI agents.
Use Cases
HappyRobot is designed around the concept of use cases. A use case is a specific scenario you want to automate.
Each use case consists of a workflow and runs. The workflow defines the steps you want to take to complete the use case. Runs are executions of the workflow.
Workflows
Every workflow starts with a trigger, which is the event that will start the workflow. After the trigger, you can add actions. Each action will be executed sequentially.
There are two types of triggers: Instant and Scheduled.
Instant: Triggers that are executed when an event occurs. For example, a webhook trigger will be executed when a webhook is received. Instant triggers have a lightning bolt icon.
Scheduled: Triggers that are executed at a specific intervals. For example, check every 10 minutes for new emails. Scheduled triggers have a dropdown selector with the interval options.
When you create a workflow from scratch, you’ll get a default empty trigger and action.
To change the trigger, click on the node and select the integration you want to use. Go to the Integrations page to learn more about the integrations available.
Same applies to actions. Click on the action node and select the integration you want to use.
You can configure a node by clicking on it and using the right sidebar. Configuring a node consists of 3 steps: setup, configuration, and testing.
Triggering Workflows & Making POST Requests
Each workflow in HappyRobot automatically generates a webhook endpoint, allowing you to trigger workflows and send POST or GET requests to the same URL whenever needed. To set up a trigger, add a new tool → Select Webhook, navigate to Setup → Test to retrieve the generated webhook URL, and use this URL to send a POST or GET request to trigger the workflow programmatically.
After a workflow completes, you may need to send its results to an external service. In this case, use a POST or GET request in the workflow and specify an external API endpoint as the URL, such as a database, third-party service, or another HappyRobot workflow webhook. This ensures seamless integration and automation across different platforms. For more details, visit the Webhook Integrations page.
Setup
During setup you need to specify the event within that integration. For example, the Webhook integration has multiple events: Polling or Incoming hook. The event defines the actual behavior of the node.
You can also change the integration of a node by clicking on the Integration input on the sidebar and selecting a different one from the modal. Note that some nodes, like AI Agents, don’t allow for this.
Some integrations require credentials, such as gmail or slack. If that’s the case, the configure step will be blocked until you enable the integration in the Account section of the setup. If you click there you will be redirected to the integrations settings page of the organization. Integrations are enabled per organization. Enable the integration and come back to the workflow to continue. You can move to the configure step by clicking the Continue button or clicking on the Configure button on the navbar.
Configure
Each event will have different configuration options. Head to the Integrations page to learn more about the integrations available. There’s a dedicated page for each integration.
Testing
Every node needs to be tested before it can be used in a workflow. The reason for this is so that the system knows what the output schema for the node is. Subsequent nodes will be able to access variables from previous nodes. The testing step informs the other nodes what variables to expect as output for that step.
You can click on the Fetch records button to retrieve the latest records from the event.
If it’s an instant trigger, make sure you trigger the event before clicking the button. For example, if you’re testing a webhook trigger, you need to send a request to the webhook URL. If you’re testing an Inbound to number trigger, you’ll need to make a phone call to the number to create a record.
If the trigger is scheduled, you can click the Fetch records button and the system will execute the trigger and fetch the records.
Variables
Every tested node will have an output schema: a set of variables that will be available to the next nodes. At runtime, the variables will take different values depending on what triggered the workflow and how it evolves.
You can use variables in most of the configuration inputs. You can type the ’@’ character to open a left popover with the list of variables, organized by node.
If you don’t know what inputs have access to variables, focus on the input and an ’@’ button should appear at the top right of the input. Clicking on it will open the variables popover.
Publishing
Once all the nodes are configured and tested, you can publish the workflow by clicking the Publish button on the top right of the workflow. If the button is disabled, it means that the workflow is not in a valid state to be published. Double check that none of the nodes have an orange exclamation mark on the graph.
Published workflows are live and immutable. This means you can’t add new actions or change the configuration of existing ones. If you need to make changes, click on the stop button on the top right of the workflow and make the changes there.