Skip to content
Nappai Documentation

Data to JSON

The “Data to JSON” component takes the information you provide and converts it into a clean, standardized format that most applications, databases, and external tools understand. This makes it much easier to store your data, share it with other systems, or pass it along to the next step in your workflow without running into formatting errors.

How it Works

When you connect this component to your workflow, it automatically checks the data you provided. It looks at whether you are working with a single piece of information or a collection of items, and then extracts the core content from it. Next, it carefully rewrites the data to ensure everything uses basic, widely compatible formats like plain text, numbers, and yes/no values. If the data contains anything that standard systems cannot read directly, it automatically converts those parts into simple text. Finally, it outputs a clean, ready-to-use structure that you can confidently connect to other parts of your automation.

Inputs

Mapping Mode

This component has a special mode called “Mapping Mode”. When you enable this mode using the toggle switch, an additional input called “Mapping Data” is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Input Fields

The following fields are available to configure this component. Each field may be visible in different operations:

  • Data: The Data object or list of Data objects to convert to JSON. This field is designed to accept both individual items and collections, making it easy to work with whatever information you are handling.

Outputs

The component produces a clean, ready-to-use data structure in JSON format. This output contains only basic, widely compatible data types, which means you can confidently send it to external applications, save it to databases, or pass it to other workflow steps without worrying about formatting errors.

Output Data Example (JSON)json

{ “id”: “user_12345”, “name”: “Alex Doe”, “role”: “manager”, “active”: true, “projects”: [ { “project_id”: “proj_a”, “deadline”: “2024-12-31” }, { “project_id”: “proj_b”, “deadline”: “2025-01-15” } ] }

Connectivity

This component is typically used as a bridge between data-generating nodes and downstream processes that require structured information. You will usually connect its output to:

  • API Senders or Webhook Nodes: To safely share data with external services.
  • Database Connectors: To store records in a format that databases easily accept.
  • Data Processors or Filters: To ensure that subsequent steps receive clean, predictable data.
  • Notification or Reporting Tools: To format information clearly for emails, dashboards, or summaries. Using this component early in your workflow helps prevent errors caused by incompatible data formats.

Usage Example

Imagine you are building a workflow that collects customer feedback from a form, then stores it in a company database. First, you collect the feedback using a form node. Next, you add the “Data to JSON” component to convert that form data into a standard format. Finally, you connect the output to your database node. The component ensures the feedback is neatly organized as text and numbers, making the storage step smooth and error-free.

Tips and Best Practices

  • Keep your input data as simple as possible before passing it to this component to ensure faster processing.
  • If you are working with large collections of items, enable Mapping Mode to handle each item efficiently.
  • Always preview the output of this component before connecting it to critical database or API nodes to verify the structure matches your expectations.
  • Use this component whenever another part of your workflow complains about receiving “complex” or “unsupported” data types.

Security Considerations

This component safely converts data without executing code or accessing external systems. However, always ensure that the data you feed into it does not contain sensitive information like passwords or personal credentials, as the converted output will be a standard data structure that could be logged or shared.