Automations
A no-code automation engine for Payload v3. Beta scaffold.
@10x-media/automations will let editors compose automations from the admin panel: pick a trigger, set conditions, order a list of actions. Developers register the trigger and action catalog in code; each action runs as a Payload task, so retries, queues, and the audit trail come from the jobs system rather than a parallel runtime.
Beta scaffold. The engine is not built yet. Installing the plugin today registers translations and records the resolved trigger catalog on the config; it adds no collections, no UI, and runs nothing.
What exists today
- The
automations(options)factory withdisabled,translations, andtriggersoptions. - A trigger catalog seam: the plugin runs last (
order: 100) and resolvestriggersafter sibling plugins have contributed. Webhooks pushes awebhooktrigger slug when both are installed. The resolved list is recorded onconfig.customunder the exportedAUTOMATIONS_CUSTOM_KEY. - The standard subpath exports:
./types,./client,./i18n. Translations follow the shared pattern (namespaceautomations:).
Install
pnpm add @10x-media/automationsimport { buildConfig } from 'payload'
import { automations } from '@10x-media/automations'
export default buildConfig({
plugins: [automations({})],
})Options
| Option | Type | Default | Description |
|---|---|---|---|
disabled | boolean | false | Return the incoming config unchanged. |
translations | TranslationsOption | none | Per-locale string overrides. See Translations. |
triggers | string[] | [] | Trigger slugs available to author automations. Sibling plugins append to this before the plugin runs. |
Where it is headed
Automations is the consumer end of the jobs family: Jobs is the runtime and ops layer, Webhooks and others contribute triggers, and this plugin turns them into editor-composable automations. Until the engine ships, use those plugins directly.