> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/files-and-tables.md).

# Files and tables

Files and tables in the automation module: upload files and use them in flows, use tables as key-value stores for mappings and markers.

**Path:** sidebar → **"Automation" → "Files"** or **"Tables"**

Flows sometimes need a place for data that outlasts a single run: a CSV file with employee data, a generated PDF, a cost center mapping or the list of entries already processed. That is what **"Files"** and **"Tables"** are for.

{% hint style="info" %}
"Files" and "Tables" only appear in the menu if they are enabled for your company. Like all automation areas, they show the content of the selected workspace ("Personal" or "Team", see [Automation at a glance](https://hub.equipme.io/dokumentation/automation.md#personal-or-team)).
{% endhint %}

## Files

**"Files"** contains all files that flows have created or that you have uploaded for flows.

| Column     | Content                                         |
| ---------- | ----------------------------------------------- |
| "Name"     | File name                                       |
| "Uploaded" | Time of upload or creation                      |
| "Flow"     | The flow the file belongs to (link to the flow) |
| "Size"     | File size                                       |

* **"Upload File"** uploads a file, e.g. a CSV list from the HR system.
* **"Download"** downloads a file, **"Delete"** deletes it.
* **"Delete All"** deletes all files in the list.
* Search ("Search …") and "Sort By" help you find files faster.

{% hint style="warning" %}
Deleted files cannot be restored. Flows that use a deleted file fail.
{% endhint %}

### Using files in flows

Flows refer to files by their **File ID**. A component that creates a file outputs this ID; the next component takes it over via a variable.

* **CSV from equipme lists:** list actions of the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md#list-actions-and-output-type) with the Output Type **"Store to CSV file"** store their result as a CSV file under "Files" – e.g. all assets for a monthly export.
* **Generate a PDF:** the [PDF](https://hub.equipme.io/dokumentation/automation/connectors/utilities.md) module creates a PDF from HTML and outputs the File ID.
* **Pass it on:** hand the File ID to e.g. **Email › Send Email** (attachment), to an upload to a cloud drive or as an attachment to an asset in equipme.
* **Use uploaded files:** components with a file field offer a file picker in the inspector ("Choose a file …", "Browse", "Upload file"). This way a flow can, for example, read an uploaded CSV file.

Example: a Scheduler starts monthly, **Equipme › List Services** (assets) stores the result with "Store to CSV file", **Email › Send Email** sends the file to accounting.

## Tables

**"Tables"** are simple data stores in which flows remember values. Each table consists of entries with exactly two columns:

| Column  | Content                                                              |
| ------- | -------------------------------------------------------------------- |
| "Key"   | The unique key, e.g. a personnel number or serial number             |
| "Value" | The associated value – text, a number or several fields as JSON text |

So tables are not spreadsheets with many columns but a "key → value" lookup.

### What for?

* **Mappings:** department in the HR system → organizational unit in equipme; location code → location ID.
* **Markers:** which employees, orders or tickets have already been processed? This prevents a flow from creating duplicates.
* **Intermediate states:** date of the last successful sync, counters, last known values for comparison.

### Creating and maintaining a table

1. **"Create store"** creates a new table.
2. Use **"Rename store"** to give it a meaningful name, e.g. "Mapping department → OU". **"Delete store"** deletes it (cannot be restored).
3. **"Add record"** opens "Create record": enter "Key" and "Value", then "Create".
4. Change existing entries with **"Edit"** ("Update record") and remove them with **"Remove"**. "Search records …" searches the entries.

A default table already exists; it can be neither renamed nor deleted.

### Reading and writing tables in flows

You find the building blocks in the flow designer under "Utilities" in the **Storage** section:

| Component                             | Purpose                                                                                             |
| ------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **Set**                               | Create or overwrite an entry (key + value)                                                          |
| **Get**                               | Read the value for a key; if the key does not exist, the message goes out via the "notFound" output |
| **Find**                              | Search entries by pattern                                                                           |
| **Remove**                            | Delete an entry                                                                                     |
| **Clear**                             | Delete all entries of a table (permanently)                                                         |
| **Save To File**                      | Save the table as a CSV or JSON file under "Files"                                                  |
| **On Item Added / Removed / Updated** | Triggers as soon as an entry changes                                                                |

The table must exist before you can select it in a component.

**Example: avoiding duplicate processing**

1. The trigger delivers a new employee.
2. **Get** with key = personnel number in the table "Processed employees".
3. "notFound" output → create the account → **Set** with key = personnel number, value = date.
4. If the key already exists, the process ends – the employee has already been processed.

## Frequently asked questions

**Where do I find the CSV file from "Store to CSV file"?**

Under "Automation" → "Files", in the same workspace as the flow. The "Flow" column shows which flow created it.

**Can I create a table with several columns?**

No, each entry has one key and one value. Store several fields as JSON text in the value and read them back in the flow with a modifier.

**Can I export a table?**

Yes, in a flow with the **Save To File** component. The file is then stored under "Files" and can be downloaded.

**Do files and tables take up storage?**

Yes. Remove files and entries you no longer need regularly.


---

# 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://hub.equipme.io/dokumentation/automation/files-and-tables.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.
