Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.script.it/llms.txt

Use this file to discover all available pages before exploring further.

Every script in Script.it is made up of blocks — the individual units of work that run in sequence when you execute a workflow. Each block does one thing, and together they form a complete automation.

​
Executable blocks

An executable block runs code when the block is executed. This is how your automation actually does things: fetches data from an API, processes a file, sends a message, transforms records, and so on.

​
What executable blocks do

When the agent runs an executable block, Script.it runs the source file for that block and shows the result in the session. The agent normally handles the implementation for you, but the source file remains inspectable if you want to review it. Each executable block has a clear label in the script view. Use those labels when you ask the agent to change a specific step.

​
Supported languages

Executable blocks support Python and shell scripts. The agent chooses the right approach for the job, so you usually don’t need to decide which language to use.

​
Output and artifacts

When an executable block runs, any files it writes become artifacts that you can inspect or download. Standard output and errors are streamed back to the chat panel so you can see what happened in real time.
Runtime artifacts — files produced during a run — are stored in the session, not the script. This means the same script can be run in many sessions without the outputs conflicting with each other.

​
Markdown blocks

A Markdown block contains plain text formatted with Markdown. It doesn’t run any code — it’s purely for documentation and notes. Use Markdown blocks to describe what a script does, explain the purpose of a group of steps, or leave instructions for teammates. They appear inline in the script view, making it easier to understand a workflow at a glance.

​
Managing blocks via chat

You never need to edit script files by hand. The AI agent creates and maintains all blocks for you based on your chat instructions.
You can ask the agent to add, edit, or remove blocks at any time by describing the change in plain English — for example: “Add a step that sends the output to Slack” or “Remove the data validation step.”
Here’s how the agent handles common block operations:
1

Adding a block

Describe the new step you want: “Add a block that reads a CSV file and filters rows where the status is ‘active’.” The agent writes the source file, creates the block, and places it in the right position in the sequence.
2

Editing a block

Describe the change: “Update the fetch block to also include the author field in the response.” The agent edits the block and its source file directly — you don’t need to open an editor.
3

Removing a block

Ask the agent to remove it: “Remove the email notification step.” The agent removes the block and updates the script.

​
Reviewing a script

The script view shows blocks in the order they run. For a weekly report script, you might see:
  • About this script — a Markdown block that explains the goal and what the script needs.
  • Fetch report data — an executable block that collects the latest data.
  • Create summary — an executable block that turns the data into a readable summary.
  • Post summary to Slack — an executable block that sends the result to the right channel.
You can click a block to review its purpose, see recent results, or ask the agent to change it.