> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/5.-artifacts/5.6-how-artifacts-flow-through-workflows.md).

# How Files Flow Through Workflows

Files move through Alludium as durable context. They can start as user inputs, support agent work, become project outputs, and then serve as references for future work.

***

## A Typical Flow

1. A user uploads source material to **Files**, a project, or a chat.
2. A task or agent uses the selected files as context.
3. The agent produces a draft, summary, table, memo, or other output.
4. A human reviews, edits, and approves the result.
5. The approved output is kept with the project or uploaded as a reusable file when it should inform future work.

This keeps the chain of context visible: source material, task execution, generated output, and reviewed result.

***

## Files in Task Work

Tasks often use files as inputs. A task may ask an agent to summarize a report, extract data from a spreadsheet, compare two documents, or produce a draft using a template.

For repeatable task types, make the expected files clear in the task description or project setup. This reduces ambiguity for users and makes remote testing flows easier to maintain.

***

## Files in Project Work

Projects use files to keep work grounded in the right context.

Project files can include:

* Briefs and source documents.
* Intermediate drafts.
* Reviewed outputs.
* Evidence or supporting materials.
* Reusable references generated during the project.

Keep files with the project when they are part of the project record. Promote them to global Files only when they should become reusable workspace knowledge.

***

## Files in Agent Work

Agents use linked or selected files to produce more consistent outputs. Files are especially important for agents that need to follow a format, apply a policy, or reuse institutional knowledge.

Use files with agents when:

* The same context is needed repeatedly.
* Output quality depends on examples or templates.
* The agent needs a stable factual reference.
* Several users should get the same baseline behavior.

***

## Files and Automations

Automations can run agents on a schedule or in response to configured events. If an automated run depends on a file, test the automation with the current file set before enabling it for production use.

Review automated outputs regularly. A stale file can create stale automated work.

***

## Next Steps

* Use **Integrations** when the agent needs live data or actions from external systems.
* Use **Automations** when work should run without a manual prompt.
* Use **Projects** when files, tasks, and outputs belong to a managed body of work.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/5.-artifacts/5.6-how-artifacts-flow-through-workflows.md?ask=<question>
```

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.