# Use Tokens in the Editor
The new **Input Attributes** view in Nected makes it much easier to access and use the token values available to your rule or workflow directly inside the editor . Whether you're working in a **JS Editor**, **Formula Editor**, **JSON Editor**, or **List Editor**, you can now search, drag, and drop attributes right where you need them — without typing or memorizing names.
### Accessing Input Attributes
Whenever you open an editor (JS, Formula, JSON, or List), you’ll now see an **Input Attributes panel** on the left side of the screen.
This panel automatically lists all available attributes for the current rule or workflow context, grouped under clear sections such as:
* **Input Attributes:** Values you've added as inputs received from the Input Attribute in rule, and from triggers (like API inputs or events) in workflow.
* **Output Data attributes:** Values coming from the output of the rule which then you can use inside the editor.
* **Additional Data Attributes:** Values you've set as addition data.
* **Global Attributes:** Shared variables available across the workspace
* **System Attributes:** Built-in values automatically managed by Nected (like timestamps, IDs, etc.)
* **Node Attributes (for workflows):** Values coming from previous nodes
### Using the Input Attributes Panel
1. **Search and Filter**\
At the top of the Input Attributes panel, there’s a search bar. You can quickly search by attribute name or filter through groups to find exactly what you need.
2. **Expand Attribute Groups**\
Click any group (for example, *Trigger Attributes* or *Global Attributes*) to view the list of available attributes. Each attribute shows its **name** and **current value** (if available).
3. **Drag and Drop Attributes**\
Once you find the attribute you want to use, simply **drag** it from the left panel and **drop** it inside the editor field.
* In **JS or Formula Editors**, attributes will appear inline within your logic.
* In **JSON or List Editors**, they will be added as part of the object or list structure.
4. **Preview Attribute Details**\
After inserting an attribute, you can **click on it** directly in the editor to view more details—such as its type, source, or current value.
5. **Editing and Validation**\
The editor automatically validates references to input attributes. If an attribute changes or becomes unavailable, it’s highlighted so you can fix it easily.
### Example Use Cases
* **In JS Editor:**\
Drag a *Trigger Attribute* like `order_id` into a formula:
```js
if ({{order_id}} > 1000) {
return 'High Value Order';
}
```
* **In JSON Editor:**\
Insert an input attribute as part of a payload:
```json
{
"order_id": {{order_id}},
"status": "confirmed"
}
```
* **In Workflows:**\
Use attributes from previous nodes (like responses or calculated values) directly in **Set Variable** or **Response** nodes.
***
The new Input Attributes view simplifies how you handle data inside Nected:
* No need to remember or type variable names
* Consistent drag-and-drop experience across all editors
* Quicker access to real-time values during workflow setup
With this update, building logic in Nected feels faster, more visual, and less error-prone.
---
# Agent Instructions: 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:
```
GET https://docs.nected.ai/nected-docs/references/pre-configured-tokens/use-tokens-in-the-editor.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.