Skip to content

How-to guides

Each guide does one job, start to finish. It tells you what you need, shows a complete script, walks through why each part is there, and ends with ways to change it. The scripts follow the habits in the tutorial’s safe event script: guard early, check the work isn’t already done, and keep output away from input.

Where a guide’s script needs a live share, mail or an outside service, the part that holds the real logic is also shown on its own, with sample data, so you can run it in the editor first.

  1. File a document into a folder named by one of its fields
  2. Rename files from their fields
  3. Send an email from a template when a field changes
  4. Log each document’s fields to a CSV
  5. Build a spreadsheet report of a folder
  1. Call a web API and store the answer in fields
  2. Tidy a folder every night
  3. Redact a PDF
  4. Respond to a webhook
  1. Use one script for several shares
  2. Test a script before it touches real files

Most guides attach a script to an event, a schedule or a webhook. Where scripts run explains each one, what it hands the script, and who the script runs as. The Limits page has the time and memory limits every run has.