How to Work with Item Data Types in Make.com

Understanding how item data types work in make.com is essential if you want your scenarios to pass information accurately between apps, modules, and tools. This how-to guide explains each built-in data type, how they behave inside bundles, and how to use them correctly when building or debugging automations.

The information below is based on the official documentation at this make.com data types article, rewritten as a practical step-by-step tutorial.

What Item Data Types Are in Make.com

In make.com, every piece of information inside a bundle has a specific data type. These data types control how values are processed, validated, mapped, and transformed across modules.

At a high level, the data types available in make.com include:

• Text
• Number
• Boolean
• Date
• Array
• Object
• File
• Unsupported

Each type has its own rules, allowed values, and typical module fields where it appears.

How Data Types Behave Inside Make.com Bundles

Every module in make.com works with bundles. A bundle is a group of key-value pairs where each value has a data type. When a module executes, it:

1. Receives one or more input bundles.
2. Processes them based on its configuration.
3. Outputs new bundles with specific data types.

Knowing the underlying type helps you avoid mapping errors and makes troubleshooting easier when a field is not accepted by the next module.

Text Data Type in Make.com

The Text data type represents any sequence of characters. In make.com, this is the most common type and appears in labels, IDs, email bodies, URLs, and more.

Key properties of Text in Make.com

• Stored as a string of characters.
• Can include letters, numbers, and symbols.
• Often contains formatted values like JSON or HTML, but is still treated as pure text.

How to use Text fields correctly

1. Map Text outputs only into Text-compatible inputs.
2. Use text functions (like concatenation or substring functions) when you need to transform the value.
3. When a module expects a Number or Date, convert the Text using appropriate functions or by reconfiguring the source module in make.com.

Number Data Type in Make.com

The Number data type represents numeric values used for counts, IDs, prices, or other calculations. In make.com, numbers can be integers or decimals depending on the source application.

Key properties of Number in Make.com

• Used in calculations and numeric comparisons.
• Cannot include non-numeric characters other than decimal separators and minus sign.
• Displayed as a number in the output fields of most modules.

How to use Number fields correctly

1. Map Number values to fields that explicitly expect numeric input.
2. Use numeric functions to add, subtract, or aggregate values.
3. If a numeric value is provided as Text, convert it with appropriate functions before using it in calculations in make.com.

Boolean Data Type in Make.com

The Boolean data type represents logical values: true or false. This is commonly used in make.com filters, conditions, and module options.

Key properties of Boolean in Make.com

• Only accepts two logical values.
• Frequently shown as checkboxes or switches in modules.
• Often used to control scenario flow (e.g., whether to execute a route).

How to use Boolean fields correctly

1. Map Boolean values into options that clearly state they expect true/false inputs.
2. Use them in filters to allow or block bundles based on conditions.
3. Avoid mapping raw Text (like “yes” or “no”) into Boolean fields in make.com without proper conversion logic.

Date Data Type in Make.com

The Date data type covers date and time values, generally stored in an ISO-like format. In make.com, date fields are essential for scheduling, timestamps, and time-based filters.

Key properties of Date in Make.com

• Represents a point in time, often including date and time components.
• Internally stored in a consistent format to allow comparisons.
• Can be converted, offset, or formatted using date functions.

How to use Date fields correctly

1. Ensure that mapped values are valid dates recognized by make.com.
2. Use date functions to add or subtract time intervals.
3. When filtering bundles, use Date comparisons rather than treating them as Text.

Array and Object Data Types in Make.com

Array and Object data types allow make.com to handle structured or nested data.

Array data type in Make.com

An Array is a list of items, all stored under one field.

• Can contain Text, Number, Boolean, or even Objects.
• Used when dealing with lists like line items, tags, or collections.
• Often processed using Iterator or Aggregator modules.

Object data type in Make.com

An Object is a structured value that contains multiple named properties.

• Represents complex entities, such as a contact record with fields for name, email, and phone.
• Each property inside the Object has its own data type.
• Frequently appears in modules that pass structured JSON payloads in make.com.

How to work with Arrays and Objects

1. Use mapping to access individual properties from an Object.
2. Use dedicated modules to split or aggregate Array values.
3. When working with webhooks, inspect the structure carefully to understand how Arrays and Objects are nested.

File Data Type in Make.com

The File data type represents binary files such as images, PDFs, or documents. In make.com, file items usually include both metadata and a reference to the actual file content.

Key properties of File in Make.com

• Contains file name, size, MIME type, and a file handle or URL.
• Used in modules that upload, download, or transform files.
• Handled differently from Text or Number fields because it represents binary content.

How to use File fields correctly

1. Map File outputs into File inputs of other modules, not into Text fields.
2. When converting files, use modules specifically designed for file operations in make.com.
3. Be aware of file size limits and supported formats of the connected apps.

Unsupported Data Type in Make.com

The Unsupported data type appears when make.com receives data in a form it does not fully recognize or cannot handle natively.

Handling Unsupported data types

• They may appear as raw values or with limited metadata.
• Whenever possible, transform or cast the value into a supported type.
• Check the original app’s documentation or adjust the module configuration to avoid Unsupported values in make.com.

Practical Steps to Choose the Right Data Type in Make.com

To use item data types effectively, follow these practical steps whenever you build or edit a scenario in make.com:

1. Inspect the output: Run the module once and review the output bundle to see the type of each field.
2. Match types carefully: When mapping, ensure the source type and target type are compatible.
3. Use functions: Apply Make functions to convert Text to Number, Number to Text, or to format Dates.
4. Handle complex structures: Break down Arrays and Objects using Iterators or JSON parsing modules.
5. Avoid silent failures: If a field does not behave as expected, re-check its data type in make.com and adjust mapping.

Optimizing Your Make.com Scenarios with Correct Data Types

When you understand how item data types work, your make.com scenarios become easier to maintain, faster to troubleshoot, and less likely to fail because of invalid inputs. Correct mapping of Text, Number, Boolean, Date, Array, Object, File, and Unsupported types ensures each module receives exactly what it expects.

For broader automation strategy, optimization, and troubleshooting across different tools (including make.com), you can also consult resources like Consultevo automation consulting to improve overall integration design.

Use this guide alongside the official item data types page in make.com to keep your scenarios clean, predictable, and robust, even as your integrations grow more complex.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help