AppsDrive

AI agents on your files · Autessa Drive

Triggers, apps and automations

Autessa Drive is also a file intake for automation. Because every file is a row, table triggers fire on every new or changed file; custom apps, scripts and the CLI upload into the same folders people browse; custom columns hold status or client IDs; and Redact saves permanently redacted PDFs straight into a drive folder.

Goes beyond a typical cloud drive
Start free
AutomationTable trigger · new or changed fileSAMPLE
01
File lands
/Intake/claim-8841.pdf
02
Trigger fires
On new file
03
Script or agent
Reads, classifies, files
04
Result saved
/Claims/2026/…
Custom apps upload hereScripts and CLI push hereRedact saves hereCustom columns: status, client_id

the-problem.md

Files arrive, then wait for someone to notice

Claims, invoices and forms land in a shared folder and sit until a person opens them. Automation should start the moment a file appears, using the same folders and permissions as everyone else.

README · what you get
  • Table triggers fire on new and changed files and can run a script or an agent.
  • Add custom columns such as status or client_id and use them in triggers.
  • Custom apps built on Autessa can upload into drive folders.
  • Scripts use the AutessaScript SDK (autessa.autessadb.drive) to list, search, read, upload, move, version and share.
  • Redact saves the redacted copy as an ordinary drive file, which follows the folder’s access and is searchable.
  • Every change made by automation is a version, so it can be reviewed and undone.

how-it-works

How does triggers, apps and automations work in Autessa Drive?

  1. 1

    Choose an intake folder

    For example /Intake, shared with the team that processes it.

  2. 2

    Add a trigger

    From the drive’s Settings, add a trigger on new or changed files.

  3. 3

    Process the file

    A script or agent reads it, fills custom columns and files the result.

  4. 4

    Review

    People see the results in the same folders, with version history.

every-option

Automation building blocks

OptionWhat it does
TriggersOn new or changed files.
Custom columnsYour own fields per file.
AutessaScript SDKdrive, drive.uploads, drive.versions, drive.shares.
Custom appsUpload into drive folders from your own app.
RedactSaves redacted PDFs into a chosen folder (default Redacted/).

permissions

Who can do what?

WhoCan
Drive owner and drive adminsAdd triggers and custom columns.
EditorRun scripts and apps that write where they have Editor access.
Agent with a Drive toolProcess files on a trigger within its scope.

AI agents

How AI agents use it

A trigger can hand each new file to an agent that reads it, extracts the fields you need into custom columns, and files it in the right folder, with every step versioned.

Agents only reach files the person they act for can open, and every agent write is a version you can undo.

About Drive tools for agents →

connected

How it connects to the rest of Autessa Drive

DRIVE FEATURE

Custom columns

Your own fields on every file.

DRIVE FEATURE

API and SDK

Build intake from any system.

AUTESSA PRODUCT

Redact

Save redacted copies into Drive.

faq.md

Questions about triggers, apps and automations

Can I run an automation when a file is uploaded?

Yes. Add a table trigger on the drive, and it fires on every new or changed file.

Can my custom app save files to Drive?

Yes. Apps, scripts and the CLI upload into the same folders people browse, following the same sharing.

Where does Redact save files?

In any drive folder you can write to, Redacted/ by default. The redacted copy is an ordinary drive file with versions, sharing and search.

Autessa Drive

Try triggers, apps and automations in Autessa Drive

Autessa Drive is also a file intake for automation: triggers fire on every new or changed file, and apps, scripts and Redact write into the same folders people browse.

Start free

100% customizable, code and all

Make Autessa Drive fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours