Skip to main content
Automations are how work happens in Fieldwork when you’re not watching. There are two kinds:

​
Agent automations

A scheduled, unattended agent run: a morning sales digest, a weekly anomaly check, a monitor that speaks up when something needs attention. Each run is a real agent turn — with your data, connectors, and knowledge base — under a locked-down tool list you approved when the automation was created. Agent automations run as their owner and are deliberately unshareable: a standing job that acts with your access stays under your control.

​
Actions

Non-conversational scheduled jobs:
  • Data syncs — scheduled connector pulls that keep your organization’s tables current (these live in the managed Data syncs folder on the Automations page)
  • Scripts — scheduled code, authored and reviewed in conversation, running in an isolated workspace with the owner’s data access and no stored secrets

​
The review card

Creating or changing any automation — even your own — goes through an approval card in the conversation. For scripts, the card shows the full source; for agents, the schedule, instructions, and tool list. Standing unattended execution is always something you explicitly reviewed, never something that crept in.

​
Runs and history

Every run is recorded. Open an automation to see its run history and results; agent-automation runs produce a readable conversation transcript you can open like any other.

​
Organizing

Automations live in the same folder tree as your other assets — organize them however your team thinks. The Data syncs folder is managed and stays put.