> 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/pro/automation/files-and-tables.md).

# Files and tables

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

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

Flows sometimes need a place to store files or remember values. That's what **"Files"** and **"Tables"** are for. Both menu items only appear if they are enabled for your company. Like flows and accounts, files and tables belong to the selected area "Personal" or "Team".

## Files

Under **"Files"** you find 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 that created the file |
| **"Size"**     | File size                      |

* **Upload:** **"Upload File"**, e.g. a mapping list as CSV.
* **Download:** **"Download"** on the file.
* **Delete:** **"Delete"** on the file or **"Delete All"** for all files. A flow can no longer use deleted files.
* **Search and sort:** via the search field and "Sort By".

### Using files in flows

* **CSV from list actions:** Many list actions of the equipme connector and the Microsoft connectors offer "Output Type" → **"Store to CSV file"**. The result is saved as a file under "Files" and passed on in the flow via its file ID – e.g. as an email attachment.
* **Reading uploaded files:** In components with a file picker, you select an existing file or upload one directly.
* **PDF documents:** The "PDF" module creates a PDF file from HTML, e.g. a handover protocol (see [Utility modules: Lists and PDF](https://hub.equipme.io/pro/automation/connectors/utilities.md)).

## Tables

Under **"Tables"** you create simple stores in which flows remember values across several executions. Each entry consists of a **key** ("Key") and a **value** ("Value") – similar to a lookup list.

**Typical uses for providers:**

* **Mappings:** Pro customer → customer number in the ERP, product → item number at the distributor, customer → name of the Intune account.
* **Markers against duplicates:** store order or invoice numbers already transferred to the ERP and check them before every transfer.
* **Intermediate states:** e.g. the time of the last successful synchronization.

### Managing tables

1. **"Create store"** creates a new table. Use "Rename store" to give it a meaningful name, e.g. "ERP customer numbers".
2. **"Add record"** adds an entry: enter "Key" and "Value", click "Create". Each key may only occur once.
3. Change entries with **"Edit"** and remove them with **"Remove"**. Use "Search records …" to search within a table.
4. **"Delete store"** deletes the whole table. **Deleted tables cannot be restored.**

Create a table **before** you select it in a flow.

### Using tables in flows

You find the components for reading and writing in the flow designer under "Utilities" in the Storage section:

| Component        | Purpose                                                                                       |
| ---------------- | --------------------------------------------------------------------------------------------- |
| **Set**          | Create or overwrite an entry (key and value)                                                  |
| **Get**          | Read the value for a key; if the key is missing, the flow continues 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"                                            |

There are also triggers that fire as soon as an entry is added, changed or removed.

**Example – transfer an invoice only once:** Trigger *New Invoice* → **Get** with the invoice number as key → via "notFound": pass the invoice to accounting and store the invoice number with **Set**. If it already exists, the flow ends.

To store several values for one key, combine them as JSON text in the value.

## Frequently asked questions

**I don't see "Files" or "Tables" in the menu.**

These areas are not enabled for your company. Contact your account manager at equipme.

**Can a table have several columns?**

No. A table stores key-value pairs. Combine several details in the value, e.g. as JSON.

**My flow can't find the table.**

Check whether the table and the flow are in the same area ("Personal" or "Team") and whether the table was created before you edited the flow.


---

# 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/pro/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.
