---
title: 'Create an automation'
description: 'Configure a small automation and verify its output before enabling triggers.'
---

# Create an automation

Use a development project with the AI extension, appropriate access, and available credits. Begin with the synthetic catalog from the [first workflow](/docs/getting-started/first-workflow).

## Configure the task

Open **AI → Automations → New Automation**. Enter `Catalog completeness review` and choose visibility appropriate to the audience. Space visibility requires selecting a space you can access; personal and project visibility have different audiences.

Use these initial instructions:

```text
Inspect the tutorial products and report records without a category.
Include each affected record's ID and SKU.
Do not change any records. If you cannot access a field, report that limitation
rather than treating the field as empty. State how many records you inspected.
```

Select a model. Keep **Mutations → Require approval**. The form shows **Memories → Always on**; previous context is separate from your instructions and attached skills.

## Attach only what is needed

Attach the catalog review skill if you created it. A read-only catalog inspection does not need the formatting tool from the custom-tool tutorial. If you add instructions requiring that tool, attach it explicitly after discovery. A tool being visible in Dashboard's catalog does not make it callable by this automation.

## Save and run manually

Save the automation and use its manual run action. New automations start Inactive; adding and enabling recurring triggers is a later step. Open the run and compare its summary with the actual tutorial data in Desk or Explorer.

A useful result identifies the records, distinguishes missing data from inaccessible data, and states its inspection scope. A green status without those results is not sufficient verification.

## Test a proposed change

In disposable data, change the instructions to propose one narrowly identified update. Run with Require approval, inspect the affected record and before/after values, and approve or reject through [Approvals](/docs/automations/approvals). Read the record afterward to confirm the outcome.

Only then configure a [schedule, entity event, or incoming webhook](/docs/automations/triggers). Check costs, access, and loop protection before enabling unattended work.


---

[View full sitemap](/docs/sitemap.md)