> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/integration-gateway-platform-reference/integration-gateway-workbench/node-reference.md).

# Workbench Node Reference

The Workbench canvas represents an integration as a diagram of connected nodes. A color, label, and icon identify each node type. When you click a node, the system opens a read-only properties panel that displays the configuration for that node.

This page describes each node type and the fields shown in its properties panel. For canvas navigation and general use, see [Integration Gateway Workbench](/integration-gateway-platform-reference/integration-gateway-workbench.md).

Every properties panel includes an **Open in Build** link that navigates to the corresponding Build page record.

## Node Types

The canvas displays four node types. Edges connect the nodes to represent the integration's execution flow:

| Node                | Represents                                                             |
| ------------------- | ---------------------------------------------------------------------- |
| **Integration**     | The root node for the integration.                                     |
| **Service Request** | Each service request within the integration.                           |
| **Field Mapping**   | A field mapping attached to a service request.                         |
| **Validation Rule** | A validation rule attached to a service request or to the integration. |

A **Value Mapping Set** does not appear as its own node. When a field mapping or validation rule references a value mapping set, that set renders within the node's properties panel.

## Integration Node

The properties panel header reads **Integration**. The panel displays the integration's configuration as read-only fields:

* **Path Name**
* **Description**
* **Active**
* **Run Async**
* **HTTP API**
* **Tags**

Integration-level hooks display in a collapsible section: Before Hook, On Success Hook, On Failure Hook, Finally Hook, Swagger Response, and Swagger Request.

### Adapter Details

The **Adapter Details** section lists the adapters bound to the integration, each with its associated configuration fields. All fields are read-only.

## Service Request Node

The properties panel header reads **Service Request**. The panel displays these read-only fields:

* **Service Name**
* **Formula Variable** — The panel shows this above the service name.
* **System**
* **Sequence**
* **Active**
* **Abort After Execute Request Failure**
* **Skip Execute If No Sub Requests**
* **Message Substitution Name**
* **Notes**
* **Tags**

### Sub-Service Requests

When a service request contains nested sub-service requests, the node displays them in a selectable table. Each row shows the **Sequence**, **System**, and **Service Name** of a sub-service request. Click a row to select that sub-service request.

### Hooks

The node shows a hook count — for example, "3 hooks" — as a compact summary rather than an expandable list. The properties panel lists the configured hooks by name in a collapsible section:

* **Before Prepare Request Hook**
* **After Prepare Request Success Hook**
* **After Prepare Request Failure Hook**
* **Before Execute Request Hook**
* **After Execute Request Success Hook**
* **After Execute Request Failure Hook**
* **After Overall Success Hook**
* **After Overall Failure Hook**

### Logic Conditions

Conditional and iteration logic displays in a collapsible section: Call If and Call For Each.

## Field Mapping Node

The properties panel header reads **Field Mapping**. The panel displays these read-only fields:

* **Field**
* **Value**
* **Value Type**
* **Sequence**
* **Active**
* **Nullable**
* **Source Record Type**
* **Source Field Name**
* **Target Record Type**
* **Target Field Name**
* **Message Substitution Name**
* **Notes**
* **Tags**

Conditional and iteration logic displays in a collapsible section: Include If and Include For Each.

### Value Mapping Set

When a field mapping references a value mapping set, the **Value Mapping Set** sub-section displays its name and a scrollable table of the value mappings in the set.

## Validation Rule Node

The properties panel header reads **Validation Rule**. A validation rule can attach to either a Service Request node or an Integration node, depending on its configuration. The panel displays these read-only fields:

* **Type**
* **Field**
* **Rule**
* **Sequence**
* **Active**
* **Abort On Failure**
* **Message Substitution Name**
* **Notes**
* **Tags**

Conditional and iteration logic displays in a collapsible section: Apply If, Apply To Each, Pass Hook, and Fail Hook.

When a validation rule references a value mapping set, its details display in the panel in the same way as for a field mapping.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://glyue.docs.sandboxbanking.com/integration-gateway-platform-reference/integration-gateway-workbench/node-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.