Overview
A Resource is a persistent data store that lives within a Space. Resources let your automations store, query, and update data across runs — so your Spaces can remember results, accumulate information over time, and connect to external data sources. Resources support several types of content:How Resources are created
Resources can be created in three ways:- Through automations
- By uploading files
- Via external services
When you describe an automation that needs to store data, Friday automatically creates the necessary Resources as part of the Space setup. For example:Friday will create a Resource in the Space to store the funding data and add new rows each time the automation runs.
Viewing Resources
Each Resource shows:
- The resource name and type
- The number of rows and columns (for tables)
- The current version number
- When it was last updated
Working with Resources
Reading data
You can ask Friday to read data from a Resource in natural language:- “Show me all rows in the Leads resource where status is Active.”
- “How many entries are in the Inventory resource?”
- “What does the Meeting Notes resource say about the Q1 roadmap?”
Writing data
Friday can add or update data in a Resource as part of an automation:- “Add a new row to the Contacts resource with name John and email john@example.com.”
- “Update the status column to Completed for row 5 in the Tasks resource.”
- “Append today’s summary to the Weekly Report resource.”
File and external reference Resources are read-only — Friday can read their contents but cannot modify files or external data through the Resource itself. To update an external resource like a Google Sheet, ask Friday to interact with that service directly.
Querying with SQL
For more complex queries, you can use syntax:- “Run a SQL query on the Sales resource to find the top 10 deals by value.”
- “Query the Events resource for all entries from the last 7 days grouped by category.”
Versioning
Resources use a draft-and-publish model:- When an automation modifies a Resource, changes are made to a draft — a mutable working copy.
- At the end of each automation run, the draft is automatically published as a new immutable version.
- Published versions are permanent snapshots that cannot be changed.
- View the full history of changes to a Resource
- Compare any two versions to see what changed
- Reference a specific version of the data
Versions are created automatically — you don’t need to manually save or publish. If an automation run doesn’t modify a Resource, no new version is created.
Limits
| Constraint | Limit |
|---|---|
| Data size per Resource | 5 MB (larger content is stored as a file reference) |
| Resource name length | 500 characters |
| Description length | 5,000 characters |