Skip to main content

Overview

Automations are item-level triggers that execute immediately when a checklist item is answered. They enable real-time responses to inspection findings without waiting for submission completion. Key Characteristics:
  • Immediate execution: Triggers fire as soon as an answer matches conditions
  • Item-level scope: Each automation is attached to a specific checklist item
  • Single condition: Evaluates one condition per automation
  • Multiple actions: Can trigger multiple actions from a single condition
For multi-condition logic that evaluates across multiple items, see Checklist Workflows.

Action Types

Automations support five action types:

Condition Operators


Create Automations

Create one or more automations for checklist items.
Request Body: Response:

Action Configuration Examples

Flag Action

Automatically flag items for review.

Notification Action

Send multi-channel notifications.

Task Action

Auto-create a corrective action task.

Follow-up Question Action

Show additional questions based on answer.

Image Capture Action

Require photo documentation.

Get Automations

Get Automations for a Checklist

Response:

Update Automations

To update existing automations, include the id field in the automation object.

Delete Automations

Response:

Execute Automation (Internal)

When a checklist item is answered, automations are executed automatically. This endpoint is typically called internally but can be used for testing.

Common Workflows

Auto-Flag Safety Violations

Conditional Follow-up Questions

When an inspector answers “No” to a compliance question, show follow-up questions to gather more details.

Temperature Alert System

Alert managers when temperature readings exceed thresholds.

Best Practices

Combine actions strategically. For critical issues, use FLAG + NOTIFICATION + TASK together to ensure visibility and action.
Automations work best with single, clear conditions. For complex multi-condition logic, use Checklist Workflows instead.
Create a test submission to verify automations trigger correctly before publishing the template to production.
Define clear flag categories to help managers quickly identify and prioritize issues.
Be selective with notifications. Over-notification can lead to alert fatigue and important issues being missed.
Maintain documentation of what automations exist and why, especially for complex templates with many triggers.

Permissions