Workflow and public Properties
Create reusable public text settings, insert them like variables, and expose required inputs in workflows and Custom Node Types.
Put changeable information in Properties #
A Property is a named text setting. Use it for business names, opening hours, public help links, or an assistant’s answer guidance instead of repeating that information in many nodes.
These exposed settings are often described as public properties: someone configuring the workflow or reusable node can supply them without rebuilding its steps. The editor’s section is labeled Properties. This does not mean the value is automatically published on a public web page. Properties are not protected credential storage.
Create a workflow Property #
- Open the workflow editor and select its workflow settings.
- In Properties, choose Add Property.
- Set Label, the recognizable name shown when selecting the Property.
- Use Info to explain what the person configuring it should enter.
- Supply Value, the text this workflow should use.
- Choose Required when the workflow must have that value before it can be enabled, then save.
| Label | Example Value | Useful Info |
|---|---|---|
| Business name | Example Studio | Public name used in greetings |
| Opening hours | Monday to Friday, 09:00–17:00 | Include the business timezone where relevant |
| Booking URL | https://example.com/book |
Full public booking address, including https:// |
| Assistant guidance | Answer from our published hours and service information | Guidance for the configured AI step; exclude credentials |
| Minimum order amount | 100 |
Plain numeric text without a currency symbol |
Required Properties need values before the workflow can be enabled. Check the validation message if saving or activation is blocked. A technically valid value can still describe the wrong business, so review copied settings for the selected organization.
Insert a Property like a variable #
Open a node field that supports expressions and use its variable picker to select the Property by label. Combine literal text and the selected Property, for example Welcome to followed by Business name.
Use the picker token itself. Typing the words Business name into a plain text field does not create a reference. Reuse the same Property in several messages or AI instructions so a later update is made in one place.
| Task | How the Property helps |
|---|---|
| Brand several messages | Insert Business name wherever the name should appear |
| Keep an assistant informed | Insert Opening hours and Assistant guidance into the AI node’s instructions |
| Compare an amount | Select Minimum order amount as the right-side Variable in Check condition |
| Configure an API request | Insert a public resource URL or department code into its request field |
Properties contain text. A numeric threshold still needs As Number in Check condition. Check that the value is numeric before depending on it. A Property does not update a message or AI step that never references it.
Property or a value from the current run? #
Use a Property for reusable configuration, such as business information. Use a received-message or node output for information specific to this run, such as the current customer’s answer or an order lookup result. Use Set Variable to name a value composed during execution.
Do not store each customer’s message by replacing a shared business Property. Map it from the source variable through the current workflow instead. See variables for source order and missing-value behavior.
Make templates easier to reuse #
Describe what a Property expects. “Public booking URL, including https://” is more useful than “URL”. Give a realistic example in Info where appropriate. When creating a workflow from a template or copy, review its Property values before activation.
Properties in custom node types #
For a Custom Node Type, Properties define the inputs its instances expose. The definition’s Property editor provides Label, Info, and Required. Values are supplied wherever the node is used rather than entered as a shared Value in that definition editor.
Inside the definition, select these Properties through the variable picker in its steps. After adding an instance to a workflow, supply that instance’s input values or select available expressions for them.
For example, a reusable Prepare service message node might expose Business name and Help URL. A workflow instance can supply a clinic’s public details, and another can supply a salon’s details while reusing the same logic.
| Where you configure it | What you supply |
|---|---|
| Workflow Properties | Labels, help text, required flags, and values for that workflow |
| Custom Node Type definition | Labels, help text, and required inputs for callers |
| Custom node instance in a workflow | Values or expressions for that particular use |
Changing the input contract can affect existing instances. Review their mappings when changing, removing, or renaming inputs.
Properties are not a secret store #
Enter connected-service credentials through the protected connection setup. Do not place passwords, tokens, or private access keys in Properties, example JSON, assistant instructions, or customer messages.
Properties can be included in exported definitions. Review them before sharing a workflow or publishing a reusable product.
Check a Property change #
Save and test a new run on the relevant branches. Confirm the intended fields use the Property, required values are populated, and copied values belong to the selected organization.
Before deleting or renaming a Property, review its references, validation messages, and affected custom node instances. Do not assume an old reference remaps itself because a similar label exists.