A PHLO is a collection of components on the PHLO canvas connected with one another to perform a task by processing data. A component is a function that performs actions in a workflow based on data configured or received via HTTP callback.

An instance of a component dragged onto the canvas is called a node. Each node can be connected to one or many other nodes to route data through the workflow.

Each component/node has configuration parameters, options, state, and variables.

  • Configuration parameters: Each component has a configuration panel that lets PHLO creators set parameters used to perform the component’s actions.
  • Options: Options are values that are defined for configuration parameters either dynamically using Liquid templates or with hard-coded values. Configuration parameters and options act like key-value pairs.
  • States: A state is a property set based on the component’s action’s output status. For example, for the Send Message component, the state can either be Sent or Failed based on the delivery of the SMS message.
  • Variables: Each component contains a list of variables that Plivo can send to a webhook as an HTTP callback. Variables are configured in the Event Callbacks section of the each PHLO’s configuration panel.

Here’s the list of all PHLO components and their respective parameters, options, states, and variables.