> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/workflow-execution/data-types-lists-missing-values-and-empty-results.md).

# Data Types, Lists, Missing Values, and Empty Results

Workflow values can be text, numbers, booleans, objects, or lists. An empty value and a missing field can cause different behavior. Use the receiving node’s schema to decide which value to send.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fx2e8VVzbKO7y7JGlJu4o%2FG022.mp4?alt=media&token=1a30d604-2a6b-4d06-ac88-7d32e26adb4c>" %}

## Before you begin

The input schema for the receiving node or API operation.

## Data types

| Term    | Definition                                                                                                                                                  |
| ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Schema  | A definition of fields, types, required values, and supported constraints. Use it to validate the shape of data; it does not establish factual correctness. |
| Object  | A structured value containing named fields. Preserve the structure when a receiver expects fields rather than formatted text.                               |
| List    | An ordered collection of values. A receiver expecting a list needs an array, not a text description of several items.                                       |
| Null    | An explicit JSON value indicating no value. It can differ from an omitted field, an empty string, or an empty collection.                                   |
| Default | A value applied under the conditions defined by a field’s contract. Do not assume that explicit null and omission both select the default.                  |

## Handle missing values and lists

1. Inspect the upstream value and its type.
2. Map a value of the required type. Keep lists as lists when the receiver expects multiple items.

![Insert a source reference from the picker, then select the field the receiving step needs.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Ki2N6RO8BAR11pFcS69f/assets/g022-g022-02-template.png)

Insert a source reference from the picker, then select the field the receiving step needs.

3. Define how the workflow should handle missing fields and empty results before continuing.

The receiving step can validate and use the value without an unintended conversion.

## Behavior and limitations

Do not use the string "null" as a JSON null value. A missing field can use a default, while an explicit null can clear a value or fail validation. Those rules are field-specific. A search that returns an empty list is not necessarily an execution error.

| Value         | Meaning                               |
| ------------- | ------------------------------------- |
| Missing field | No value was supplied for that field. |
| `null`        | An explicit JSON null value.          |
| `""`          | Empty text.                           |
| `[]`          | A list with no items.                 |
| `{}`          | An object with no fields.             |

## Related resources

[Map variables and expressions](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/map-variables-and-expressions.md)

[Execution Order and Node Dependencies](https://docs.stackai.com/technical-reference/workflow-execution/execution-order-and-node-dependencies.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/workflow-execution/data-types-lists-missing-values-and-empty-results.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
