Build Concierge Glossary

Welcome to the Build Concierge glossary, which defines all the need-to-know terms to help you to get familiar with the Build Concierge platform!

Workflow Builder

The Workflow Builder is the overall tool used to create, manage, and configure automated workflows, including the Workflow Editor, node library, and workflow settings.

See also: Workflow Editor, Workflow, Workflow Library

Workflow

An automated process made up of connected nodes in the Workflow Builder. Workflows are triggered by starting actions, move data between systems, perform tasks automatically, and reduce the need for manual effort.

See also: Node, Mapping

Workflow Editor

The interactive canvas within the Workflow Builder where workflows are designed. Here you add, move, connect, and configure nodes to define the workflow’s logic.

See also: Workflow Builder, Node, Properties panel

Workflow Library

The Workflow Library serves as a directory within your account, listing all workflows you’ve created along with key details such as status, last run, and version information. From here, you can view, edit, enable, or disable workflows.

See also: Workflow, Workflow Builder

Workflow Overview Page

This is a dedicated page for each workflow in your Build Concierge account, showing high-level details such as its name, description, status, last run, run history, and available versions.

See also: Run History, Version History

Starting Action

A special type of node that triggers a workflow. Starting actions define when and how a workflow begins.

Action

A node that performs a task after a workflow has started, such as updating records, sending messages, or transforming data.

Node

Nodes are the building blocks of a workflow. They include Starting actions (which trigger a workflow) and Actions (which perform tasks). Each node represents a single step, such as extracting text, transforming data, sending notifications, or creating records in an external system.

See also: Workflow Editor, Properties panel, Node library

Node library

The Node Library is the catalogue of available nodes, including Starting actions and Actions, that you can add to a workflow in the Workflow Editor.

See also: Workflow Editor, Node

Properties panel

The panel where you configure the selected node’s settings, inputs, and mappings.

See also: Workflow Editor, Node, Configuration panel

Output Value

A specific piece of data produced when a node runs. Output values are made available as variables so they can be mapped into later nodes in the workflow.

Variable

A placeholder for data that flows through a workflow. Variables store output values produced by nodes — such as customer names, emails, or AI responses — and allow that data to be reused in later steps.

See also: Custom Variable, Mapping, Output Value

Custom Variable

A variable created within a node’s configuration to capture specific data from an input or output. Custom variables can then be reused later in the workflow to drive actions or populate fields.

See also: Variable, Output Value

Mapping

Mapping is the process of assigning variables (which contain output values from earlier nodes) to fields in another node’s configuration.

See also: Variable, Custom Variable, Output Value

Outcomes

The result produced when a node runs. Outcomes determine how the workflow continues and allow branching logic by connecting different nodes to different outcomes. Common outcomes include Complete and Failed.

See also: Node

Status

Indicates whether a workflow or workflow run is active, inactive, complete, or failed.

Run History

A record of all runs for a specific workflow, showing when each run occurred, its Status (complete, failed), and any outputs, logs, or errors generated.

See also: Workflow Overview Page, Version History, Status

Version History

A log of saved workflow versions, allowing you to view changes over time, compare versions, and restore a previous setup if needed.

See also: Workflow Overview Page, Run History

Regex (Regular Expression)

A regular expression (Regex) is a pattern used to search for, match, or extract specific text formats (such as email addresses, phone numbers, or reference numbers). Regex is used in the Extract Text node to define what data should be captured.

See also: Variable, Custom Variable, Mapping

Contact (BigChange)

This is the CRM contact record in BigChange. It will usually be the name of a company/organisation or an individual.

Contact note (BigChange)

Information or tasks stored against a specific contact record in BigChange. Contact notes help track communication, actions, and context related to that contact.

See also: Contact, Contact ID

Contact Group (BigChange)

Groups used to organise contacts eg. Customers' head office, Customers' depots, Staff, Suppliers.

See also: Contact

Contact ID (BigChange)

A Contact ID in BigChange is simply the unique identifier assigned to a contact (like a customer, supplier or site). It’s used to distinguish that contact in the system and reference it in jobs, schedules, and records.

See also: Contact, Contact note

Contact Reference (BigChange)

A short code or label (often chosen by the user) used to help identify a contact. Unlike the contact ID, this is usually editable and more human-friendly.\