Key Terms of Actions

Key Terms of Actions

An action is a single task in a workflow. Actions consist of input and output ports. Input ports are used to receive data, while output ports send data via connection to another action. An action is basically a code in the system. Input ports are mapped to input parameters of a function in code when output ports are mapped to the return values. ReBid CDP can be extended by programmers who write code and map it with action, which later on is visible in the workflow editor as nodes.

Action ports

An action node can have only one input port and many output ports. A port that returns no data will not trigger the next node execution. 

Action internal state

Each action node has a reference to the following data:
  1. id - node id
  2. debug - flag that tells if the node is in the debug mode
  3. event - currently processed event
  4. profile - currently processed profile. Profile may be empty if the event that is being processed is a profile-less event. 
  5. session - current user session
  6. flow - flow diagram
  7. node - information on the current executing node. With information on the inbound and outbound edges.
  8. console - the object where you can log errors and warnings.
  9. metrics - metrics object

Action core methods

An action node has 3 core methods:
  1. build - asynchronous method for action building
  2. init - synchronous action constructor
  3. run - methods that runs the action

Auxiliary functions

An action should also have a set of auxiliary functions that help ReBid CDP with action registration and data validation. Those functions are:
  1. register - it should return a Plugin object with information on action specification, metadata, etc.
  2. validate - how to validate the configuration data
    • Related Articles

    • Key Terms

      ReBid CDP makes use of various terms to refer to some actions being performed on the platform. Here are some of the key terms used in ReBid CDP: Customer data platform (CDP): A CDP is a solution that helps businesses collect, unify, and activate ...
    • Actions and Triggers

      An "Action" in ReBid CDP is a trigger the user performs by taking actions on the ReBid CDP Platform. Actions can do things like getting information or sending it to another step. Imagine an Action as a computer program. Just like a program has input ...
    • Core Definitions

      By understanding these key terms, you can use ReBid CDP more effectively: Traffic ReBid CDP can receive and send data. Therefore, the system defines two types of traffic: Incoming, i.e. systems that are able to send data to ReBid CDP. These will be ...
    • Introduction to Workflows

      Marketing automation workflows are a systematic sequence of actions and conditions designed to automate and optimize various marketing tasks. These workflows enable businesses to engage with their target audience in a targeted and personalized ...
    • Types of Profile Merging

      Profile merging is the process of bringing together multiple customer profiles that belong to the same person but have been stored separately for various reasons, like using different devices or email addresses. To create a complete profile, a unique ...