There are a few terms and keywords throughout Pendula and our Help Centre which are useful to understand.
| Term | Definition |
| Tenant |
A tenant is a Pendula environment unique to your business or organisation. Connecting your tenant to your data source allows you to start using that data within Pendula flows. |
| Object |
An object provides the overall structure for storing and interacting with your data source in a particular context. Think of an object as a table consisting of rows and columns. |
| Field |
A field is a point of data within an object, such as a first name or mobile phone number. Think of a field as a column within your table of data. |
| Record |
Each unique set of data for an object is stored as a record. Think of a record as a row within your table of data, containing all the values for each column on that table. |
| Related object |
Related objects point Pendula to the relevant recipient within your data source. They help establish what the context of your flow is, and who should receive any SMS or email communication. See Related objects for more information. |
| Flow |
A flow is an automated customer journey sent by Pendula. It can be either schedule-based (once-off or repeating) or triggered by external events and might involve one or many contacts, depending on the chosen criteria. See Flow setup for more information. |
| Rules |
Rules are used to set your contact filters or flow criteria, and reference objects, fields and values from your data source. See Flow criteria for more information. |
| Groups |
Groups are formed by two or more rules and can be used to introduce more complex logic within flow criteria. See Flow criteria for more information. |
| Node |
Nodes represent actions a flow can take once triggered. You build conversations or experiences within Pendula by dragging and dropping nodes onto the flow builder canvas and connecting them to form a logical sequence of actions. See Flow builder overview for more information. |
| Experience |
An experience tracks the unique journey of a record (or recipient) as they progress through the nodes you have configured within a flow. See Experiences and messages for more information. |
| Message |
A message contains the contents of an outbound or inbound node within an experience. See Experiences and messages and Message records within Salesforce for more information. |
| Template |
Templates form the content (or body) of messages sent from Pendula, and can be applied to one or many different flows. See Templates for more information. |
| Console |
The console provides a Salesforce user with a simple way to send ad-hoc or manual SMS to a recipient record, and contains a history of any previous conversation via SMS. See Sending SMS via the console for more information. |