Skip to content

Built-in integrations#

This section contains the node library: reference documentation for every built-in node in REA Automation, and their credentials.

Node operations: Triggers and Actions#

When you add a node to a workflow, REA Automation displays a list of available operations. An operation is something a node does, such as getting or sending data.

There are two types of operation:

  • Triggers start a workflow in response to specific events or conditions in your services. When you select a Trigger, REA Automation adds a trigger node to your workflow, with the Trigger operation you chose pre-selected. When you search for a node in REA Automation, Trigger operations have a bolt icon Trigger icon.
  • Actions are operations that represent specific tasks within a workflow, which you can use to manipulate data, perform operations on external systems, and trigger events in other systems as part of your workflows. When you select an Action, REA Automation adds a node to your workflow, with the Action operation you chose pre-selected.

Core nodes#

Core nodes can be actions or triggers. Whereas most nodes connect to a specific external service, core nodes provide functionality such as logic, scheduling, or generic API calls.

Cluster nodes#

Cluster nodes are node groups that work together to provide functionality in an REA Automation workflow. Instead of using a single node, you use a root node and one or more sub-nodes that extend the functionality of the node.

Credentials#

External services need a way to identify and authenticate users. This data can range from an API key over an email/password combination to a long multi-line private key. You can save these in REA Automation as credentials.

Nodes in REA Automation can then request that credential information. As another layer of security, only node types with specific access rights can access the credentials.

To make sure that the data is secure, it gets saved to the database encrypted. REA Automation uses a random personal encryption key, which it automatically generates on the first run of REA Automation and then saved under ~/.rea/config.

To learn more about creating, managing, and sharing credentials, refer to Manage credentials.