Core concepts

Before you start building on Script.it, it helps to understand the key ideas behind how the platform works. This page explains each core concept in plain terms — no technical background required.

​

Workspaces

A workspace is a shared place for collaboration. It holds scripts, members, triggers, and shared integrations. Workspaces have two roles:

• Editors can edit scripts and invite or remove members.
• Readers can view and run scripts and use shared integrations, but cannot change workspace content.

Workspaces also control which scripts are visible to which people. You can keep personal scripts in your private workspace and create team workspaces when you want others to use or maintain the same automations.

​

Scripts

A script is an automation workflow. It defines a sequence of steps to carry out, what each step does, and in what order. Scripts are stored in a workspace and can be run manually, on a schedule, or triggered by an external event. Each script has its own page where you can review its blocks, source files, reusable files, and recent changes. The AI agent manages the underlying setup for you, but you can still inspect what it creates. Scripts are reusable. You can run the same script multiple times, share it with teammates, or use it as the starting point for a new workflow.

​

Blocks

Blocks are the individual steps inside a script. Each block does one thing, and a script runs its blocks in order. There are two types of block:

• Executable blocks — these run code, usually Python or shell, to perform an action, such as fetching data from an API, transforming a file, or sending a message.
• Markdown blocks — these contain documentation or notes. They don’t run code, but they help you and your team understand what a script does.

When you describe a workflow to the agent, it figures out what blocks are needed and writes the code or notes for each one. You can ask the agent to add, remove, or change individual blocks at any time.

​

Assets

Assets are files stored with a script. They persist across sessions and travel with the script when it is exported or shared through a workspace. Use assets for templates, seed data, configuration, reference files, and small state files that a script should remember between runs. Files produced during a run are different: they belong to that session’s data_files/ folder and do not automatically become script assets. See Assets for examples, including how to use assets as persistent script memory.

​

Sessions

A session is a single conversation with the AI agent. Every time you open a new chat, you’re starting a new session. Each session runs in its own isolated working directory, so files created during one session don’t interfere with another. However, changes to scripts — like creating or editing a workflow — are saved to the script’s workspace and visible across all sessions that can access it. Think of a session as the working context for a particular task. You can use it to build a new script, debug an existing one, or run a one-off automation. When a trigger fires a script automatically, Script.it creates a new session to run it.

​

Triggers

A trigger is a rule that runs a script automatically in response to something happening. Instead of clicking Run manually, triggers let your automations take care of themselves. Script.it supports three types of trigger:

• Schedule — runs your script at a set time or on a recurring basis. You can use presets, plain-English timing, or a cron expression when you need a custom schedule.
• Webhook — runs your script when an external service sends an HTTP POST request to a unique URL that Script.it provides. This is useful for connecting tools that support webhooks.
• Integration event — runs your script in response to something happening in a connected tool, such as a new email arriving, a form being submitted, or a row being added to a spreadsheet.

See Triggers for setup instructions for each type.

​

Integrations

An integration is a connection to a third-party service. Script.it supports 600+ integrations including Slack, Gmail, Google Sheets, Notion, HubSpot, Airtable, and many more. Once you connect an integration, your scripts can read from and write to that service. For example, a script could pull data from a Google Sheet, process it, and post a summary to a Slack channel — all without you copying or pasting anything. You can keep a connection private or share it with a workspace. A shared connection lets every member call the service using the sharer’s account. A shared custom integration type lets members connect their own credentials through the same API definition. See Integrations for the full list of supported tools and connection instructions.

​

The agent

The agent is the AI at the heart of Script.it. It builds, edits, and runs scripts in response to your chat messages. When you describe what you want to automate, the agent writes the blocks, sets up the workflow, and can run the script right in your session so you can see what happens. You can keep chatting to iterate — ask it to add a step, fix a bug, explain what a block does, or try a different approach. The agent is designed to be transparent: every action it takes shows up in your chat, and the scripts it creates are yours to inspect and modify.

​

Credits

Credits are the usage-based currency that tracks the cost of running Script.it. AI usage (chat, building scripts, running automations) and execution time both consume credits. Your account starts with free included credits. When you need more, you can upgrade to a paid plan or purchase credits on demand. You can check your credit balance and usage history in the Account section of your workspace. See Billing & credits for details on plans and pricing.