> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-save-data.md).

# Workflow Framework: Save Data

The system automatically saves workflow data that has been modified during a task. However, you must explicitly trigger data saving when additional changes are applied to workflow data. You do this by adding a *Workflow: save data* node to your logicnet.

1. Right-click on the viewer to add a node to your logicnet.
2. Click *add node*
3. Select *Workflow: save data* from your node options list. The system adds the node to your logicnet.
4. Select the node and open the *Parameters* tab to configure it.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c6dc831c0aed5ac0279d53d374cd8967c1f31634%2F998fed0b-ca9a-40d6-be28-b7d8bdf1c35f.png?alt=media)

## Editor Fields

| Field Name  | Description/Use                                                 | Type/Options | Optional/Mandatory |
| ----------- | --------------------------------------------------------------- | ------------ | ------------------ |
| Workflow ID | This is the ID of the workflow to which the data must be saved. | Text         | Mandatory          |
| Data        | This is the data object that holds the data to be saved.        | Data Object  | Mandatory          |
| Error       | This is the data object for storing errors if they occur.       | Data Object  | Optional           |


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-save-data.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.