Skip to main content

​
A

​
Agent

An AI entity that follows a Skill’s instructions to perform tasks within a Space. Agents handle the actual execution of each step in your automation.

​
Artifact

Any content generated by an automation and stored in the Library — reports, summaries, data exports, and other output files.

​
Automation

The complete workflow that Friday manages on your behalf, packaged as a Space.

​
E

​
Environment Variable

A key-value pair stored in Settings that provides configuration to your Spaces — typically API keys, tokens, or other credentials that integrations need to function.

​
I

​
Integration

A connected third-party service (such as Slack, GitHub, or Jira) that a Space uses to access data or perform actions. Integrations are authorized via OAuth and managed in Settings.

​
L

​
Library

The central location where Friday stores all content generated by your automations. You can browse, search, share, and download artifacts from the Library. See Library.

​
O

​
OAuth

A secure authorization method that lets you grant Friday access to third-party services without sharing your password. When you connect an integration, you are redirected to the service’s authorization page where you approve specific permissions.

​
R

​
Resource

A structured data table within a Space that stores, queries, and updates data — similar to a lightweight database. Resources support SQL queries and maintain immutable version history. See Resources.

​
S

​
Session

A single execution run of a Space. Each session records every step the automation took, what data it processed, and what output it generated. You can review sessions to monitor and debug your automations. See Sessions.

​
Skill

A reusable set of instructions that tells a Friday agent how to perform a specific type of task. Skills define what tools an agent can use, how it should approach problems, and what output to produce. See Skills.

​
Space

The core building block of Friday — an automation that contains a trigger, processing logic, integrations, and output delivery. When you describe what you want Friday to do, it creates a Space to manage it. See Spaces.

​
T

​
Trigger

What starts an automation. Triggers can be time-based (a schedule like “every weekday at 9am”), event-based (when something happens in a connected service), or manual (you ask Friday to run it).