← Back to Knowledge Base

Using Automations

Getting Started

Using Automations

Automations tell Notoria what to do after a document has finished processing. You can use them to classify document types, extract structured fields, call webhooks, apply tags, move documents, and notify your team.

Where to find automations

Open Automations in the workspace sidebar. Admins can:

  • create and edit automations
  • manage the step library
  • set the workspace default automation
  • assign specific automations to document types

Admins can also open Automation Marketplace to import curated bundles, automations, step definitions, and document types into the workspace.

How automation assignment works

Each document type has an automation mode:

  • Use workspace default - the document will run the workspace's default automation
  • Use specific automation - the document will run the automation you assign to that document type
  • No automation - the document will not run any automation after processing

If a document has no document type, Notoria uses the workspace default automation when one is available.

How automations are organized

An automation is made of steps arranged into stages.

  • Steps inside the same stage run in parallel
  • Stages run from top to bottom
  • You can reuse the same step template in multiple automations

Common step types include:

  • AI Extraction - extract a value and optionally save it to a field
  • AI Classification - choose one or more options from a defined list
  • AI Validation - return a pass/fail result
  • Document Type Classification - set the document type automatically
  • Webhook - send the document context to an external service

Viewing automation results

Open any document to see:

  • which automation was resolved for that document
  • whether it came from the document type or the workspace default
  • the latest automation run
  • recent run history

If no automation will run, the document page explains why.

Marketplace Imports vs Local Automations

Marketplace items are starting points. After import, they become local workspace records:

  • imported automations can be edited like any other automation
  • imported step definitions become local step templates
  • imported document types can be assigned to documents and automations

For more on the curated catalog, see Automation Marketplace.