Skip to navigation

Workflows & Automations

Automate actions on custom object records — on creation, on field changes, or on a schedule.

View as Markdown

Custom objects have full workflow support. You can build automations that trigger when records are created or updated, run on a recurring schedule, or fire based on specific field conditions. This is where custom objects go from a structured database to an active part of your operations.

To create a workflow: go to Settings → Enterprise automation → Workflow library, select Organization or a workspace the object type is available in, open the object type’s tab, and click Create.

If the object type is tagged to more than one workspace, its workflows are fully editable in the object type’s home context and read-only in the other workspaces it’s tagged to.


Trigger Types

Record created

Fires when a new record of this type is created — by a person, by another automation, or via the API.

Use for: welcome notifications, kickoff actions, creating linked records in other systems, logging the creation event to an audit trail.

Example: When a new Vendor record is created, email the procurement team lead so they can start vendor onboarding.


Record updated

Fires when any field on a record changes, or when a specific field changes.

By default, any field update triggers the automation. Narrow it with conditions:

  • Trigger only when a specific field changes (e.g. fire only when Status changes, not when Notes is edited)
  • Trigger only when a field changes from a specific value to another (e.g. fire only when Status changes from Active to Renewal Pending)

Use for: status-change notifications, escalations, handoffs between teams when a record moves through a lifecycle.

Example: When a Contract’s Status changes to Renewal Pending, email the Owner and the procurement team to start the renewal process.


Scheduled — recurring

Fires on a repeating schedule: hourly, daily, weekly, or monthly. You define the interval and can specify the time of day and timezone.

Use for: periodic reviews, data hygiene, recurring reports, proactive alerts based on date fields.

Example: Every day at 8am, find all active contracts where End Date is within 30 days and send a reminder to each contract’s Owner.

Example: Every month on the first, find all Vendor records where Status is Active and Renewal Date is in the past, and email each vendor’s manager to review it.

Scheduled workflows are always recurring; there’s no one-time scheduled run. The Repeat setting controls whether the workflow can run on the same record again or only once. If you choose Only once, the schedule keeps running, but each matching record is processed only once across all runs.

A scheduled workflow needs at least one filter, which narrows down the records each run looks for.

Deleting a record doesn’t trigger a workflow.


Condition Filtering

Every trigger type supports condition filters that limit which records the automation acts on. For scheduled workflows, at least one filter is required.

Conditions can check:

  • Whether a field equals, contains, or matches a value
  • Whether a field is empty or filled
  • Whether a field changed from one value to another (for update triggers)
  • Whether a relationship field links to a specific person or record

Conditions are evaluated at trigger time. An automation with a condition only runs when both the trigger fires and all conditions pass.

Example: A scheduled daily automation that checks End Date is within 30 days only sends reminders for contracts actually expiring soon — not every contract in the system.


Actions

Workflow actions available on custom objects:

  • Condition — branch the workflow based on record values
  • Wait — pause before the next step
  • Skip workflows
  • Send an Email — email users, or a person picked from the record using a placeholder (e.g. the contract owner)
  • Send notification to web extension — send an in-app notification to users or placeholders
  • Make an HTTP request — send record data to an external system
  • Execute code — run custom logic
  • Classify content with AI — categorize text from the record
  • Get Atomicwork user details — look up a user’s details for later steps
  • Invite user — invite a user to Atomicwork
  • Actions from your connected apps

Custom object workflows can’t update fields on records, create service requests, or send records for approval.

When building actions, you can reference field values from the record using variables in the form {{custom_object.<field reference key>}} — for example, {{custom_object.display_id}} or {{custom_object.end_date}}. Values from relationship fields use a longer path, so pick them from the data picker instead of typing them.


Practical Examples

Contract expiry reminders

Two automations working together:

  1. 60 days out — scheduled daily, condition: End Date within 60 days AND Status is Active. Action: email the Owner that the contract is coming up for renewal.
  2. 30 days out — scheduled daily, condition: End Date within 30 days AND Status is Active. Action: email the procurement team with the contract details so they can start the renewal.

New client kickoff

Trigger: Record created on the Client object type. Action: email the onboarding team lead with the client name, tier, and account owner, so onboarding starts without anyone having to pass the news along manually.