A

Actions

Nodes

A node category that carries out designated functions after a trigger activates it. Actions are subdivided into data, messaging, and workflow types, each performing specific tasks within a flow.

See Introduction to Experience and Workflow Studio

Active

Flow Lifecycle State

The state of a flow that is currently executing tasks and engaging with recipients as per its configuration.

See Manage individual flows in various states

Activity Sync

Concept

A mechanism that compiles and aligns all user interactions within a flow into a centralised system of record, capturing data in JSON format for analysis or compliance.

See Getting data in and out of Pendula

API token

Concept

An API token is a security credential that allows other services to securely send inbound payloads to Pendula. When using webhooks to trigger an experience, it is essential that the payloads are secured by an active API token. This ensures that the data sent to Pendula is authenticated and authorised, ensuring the integrity of the communication between applications.

See Webhook trigger: Setting up an API token

Archive

Flow Lifecycle State Command

The command to hide the flow from the main list to reduce clutter while keeping data accessible.

See Manage individual flows in various states

Archived

Flow Lifecycle State

The state of flows that are no longer active but are kept for historical reference or possible reactivation, not displayed in the default list.

See Manage individual flows in various states

C

Canvas

Nested pane

A component of the Flow Builder where users visually arrange and define workflows by adding and configuring nodes.

See Complete overview of the Flow Builder

Credential

Concept

Credentials are the pieces of information, often a username and password, that are used to identify you as the authorised user of an external application.

See Make a web request: Authentication

Criteria filter

Criteria filter checks incoming data against the provided criteria. If the data matches your criteria, the experience continues along the success path. If the data does not match your criteria, the experience continues along the fail path.

See Criteria Filter and Criteria Split Workflow Actions

Criteria split

Criteria split enables you to build multiple 'criteria paths', and checks recipients against the criteria for each path. If the criteria match, the data follows the corresponding path. If multiple path's match, the highest priority (top) path is followed. If no paths are matched, they follow the 'Other' path.

See Criteria Filter and Criteria Split Workflow Actions

D

Delete

Flow Lifecycle State Command

The command to permanently erase a flow and all of its associated data from Pendula.

See Manage individual flows in various states

Draft

Flow Lifecycle State

The state of saved flows that are not yet in execution, pending further editing or activation.

See Manage individual flows in various states

Drain

Flow Lifecycle State Command

The command to cease initiating new experiences within a flow while allowing ongoing experiences to reach their conclusion.

See Manage individual flows in various states

Draining

Flow Lifecycle State

The state of flow that indicates the completion of active experiences without initiating new ones, leading to the flow's deactivation.

See Manage individual flows in various states

Duplicate

Flow Lifecycle State Command

The command to create an exact replica of a flow, which can then be modified or used as needed without affecting the original.

See Manage individual flows in various states

E

Edit

Flow Lifecycle State Command

The command to modify the configuration of a flow, including its triggers, actions, and other settings.

See Manage individual flows in various states

Error

Concept

An error is something that will prevent a node or a flow from executing successfully. Examples include misconfigured connections or merge fields that reference missing data.

See Flow errors

Error

Flow Lifecycle State

The command to create an exact replica of a flow, which can then be modified or used as needed without affecting the original.

See Manage individual flows in various states

Experiences

Concept

The individualised path a recipient takes through a flow, shaped by their responses and interactions with each node, tailoring the flow to their specific actions.

See Introduction to Experience and Workflow Studio

F

Flow

Concept

A structured sequence of nodes, beginning with a trigger and followed by actions, designed to automate processes based on event occurrences.

See Introduction to Experience and Workflow Studio

Flow builder

Page

A visual interface within Pendula for creating and adjusting flows, featuring a drag-and-drop function to facilitate the design of complex workflows.

See See Complete overview of the Flow Builder

Flow details

Page

A detailed view of a specific flow, presenting comprehensive information including version history and node configurations for lifecycle management.

See Introduction to Experience and Workflow Studio

Flow overview

Nested pane

Displays the flow’s design and configuration, which is not editable in this view but gives a snapshot of the flow's structure.

See Navigate the Flow details page

Flow version

Nested pane

Displays the historical iterations of a flow within Pendula, documented for review or reversion. Each version captures a snapshot of the flow at a point in its development or modification.

See Using flow versions in workflow studio

Flows

Page

An interface in Pendula for accessing and managing all user flows, providing an overall view of each and options for creation or modification.

See Introduction to Experience and Workflow Studio

H

Handlebars

Page

Handlebars is a templating engine that uses templates and an input object to generate HTML or other text formats.

See Working with Merge Fields in Workflow Studio

Hubs

Concept

Central interfaces within Pendula for integrating channels, data connectors, and third-party services. They enable seamless integration and management, enhancing the platform's interoperability.

See Getting data in and out of Pendula

I

Instant

Concept

An instant refers to a specific point in time that serves as a reference for calculating timestamps. This could be the current date and time or the start of an experience.

See Working with Types: Formula, Fields and Values

M

Make a web request

Make a web request is an action node in Pendula that facilitates HTTP communication with external services during an experience.

See Make a web request Data Action

Merge fields

Concept

Merge fields are dynamic values that are replaced with the recipient-specific value when a flow goes live. The recipient-specific value is determined by the data brought into the flow.

See Working with Merge Fields

N

Nodes

Concept

Individual steps in a flow that either are either triggers or actions, collectively forming the automated sequence known as a flow.

See Introduction to Experience and Workflow Studio

P

Path

Concept

A path refers to a sequence of steps or nodes that data follows within a flow, leading to different outcomes based on specified criteria or interactions.

See Complete overview of the Flow Builder

Payload

Concept

A payload is the data sent from one application to another when an event occurs. This data is included in the body of the HTTP request and typically contains detailed information about the event that triggered the webhook.

See Webhook trigger node

S

Studio

Concept

The core in Pendula for building, editing, and overseeing flows, integral to the operation of the platform.

See Complete overview of the Flow Builder

T

Terminate

Flow Lifecycle State Command

This flow lifecycle state change command discontinues a flow permanently, preventing any further activities or reactivation.

See Manage individual flows in various states

Terminated

Flow Lifecycle State

The state of flow that indicates a flow has been stopped and is not operational, remaining accessible for record-keeping but unable to be restarted.

See Manage individual flows in various states

Toolbar

Nested pane

A part of Flow Builder interface where you can browse and select different nodes.

See Complete overview of the Flow Builder

Trigger

Nodes

A node that initiates a flow in response to certain events, such as incoming messages, starting the sequence of the flow's actions.

See Introduction to Experience and Workflow Studio

U

Unarchived

Flow Lifecycle State Command

The command to restore a previously archived flow to the default view, without reactivating it.

See Manage individual flows in various states

W

Webhook

Concept

Webhooks are commonly used to connect two different applications, where an event in the source application sends serialized data, in JSON format, about that event to a webhook URL in the destination application, prompting an action (starting an experience) based on the received data payload.

See Webhook trigger node

Webhook trigger

The webhook trigger node listens for information in real-time from an external application to trigger a Pendula flow. 

See Webhook trigger node

Webhook URL

Concept

Webhook URL is a specific type of HTTP callout URL used for webhooks, where the URL is designated to receive automated HTTP requests triggered by specific events in the source system.

See Webhook trigger: Configuring Pendula with third party applications