> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/es/acciones/workflow-concepts/workflow-steps/logic-steps/json.md).

# Formatear JSON

Formatea la salida como JSON

## ¿Cómo funciona el paso JSON?

El paso JSON te permite estructurar la salida de tu flujo de trabajo en un formato JSON estandarizado. Esto se hace seleccionando las claves y los valores de los distintos pasos que deseas exponer en la salida.

## Cómo configurar un paso JSON

El paso JSON es bastante intuitivo. Dado que estás formateando la salida de un paso anterior, normalmente fluirá directamente a tu paso Final.

Puedes poner el "key" y el "value" como prefieras, y puedes elegir completarlos con la entrada de pasos anteriores:

{% @arcade/embed url="<https://app.arcade.software/share/BtyQUAfSJf5dzhIWUVIR>" flowId="BtyQUAfSJf5dzhIWUVIR" %}

<figure><img src="https://3036434873-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-7b8188ce843909fe405e83d5bd8da8eecfc8f8f8%2Fformat-json-01-step-config.png?alt=media" alt="Format JSON step with a JSON template that references an earlier step&#x27;s title and summary"><figcaption><p>Format JSON construye un objeto JSON válido a partir de salidas anteriores.</p></figcaption></figure>

Al hacer clic en el **"Añadir variable +"** botón te permitirá definir campos adicionales dentro de tu salida JSON.

## Ejemplo

Veamos un ejemplo rápido de cómo usar un paso JSON para lograr la salida que deseamos en formato JSON.

Nuestro flujo de trabajo toma una entrada de cadena simple (nombre de la ciudad) y utiliza un paso LLM para generar una breve descripción histórica de la ciudad. Insertaremos nuestro paso JSON después de esto, formateando nuestra salida como:

```
{
  "city_name": "Los Ángeles",
  "description": "La descripción completa de la ciudad."
}
```

{% @arcade/embed url="<https://app.arcade.software/share/2XKC3NgLFXFs5zJYKZNJ>" flowId="2XKC3NgLFXFs5zJYKZNJ" %}


---

# 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.airops.com/docs/es/acciones/workflow-concepts/workflow-steps/logic-steps/json.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.
