- What is goldnead/statamic-automations?
- goldnead/statamic-automations is a Statamic addon that adds a visual automation layer inside the Control Panel. It lets you build event-driven rules that trigger on content saves, form submissions, or schedules, then run notifications, webhooks, and custom jobs. It also supports custom triggers and actions for project-specific workflows.
- How do I install goldnead/statamic-automations in a Laravel app?
- Install it as a Composer package in a Laravel application that runs Statamic, then follow the addon documentation for publishing configuration and registering the addon. Recent releases do not introduce a data migration, but you should confirm the current install steps in the README. Resolve the goldnead/statamic-flow-canvas ^1.6.1 dependency before testing the visual builder.
- Which Laravel, Statamic, and PHP versions are supported?
- The provided context does not list an exact Laravel, Statamic, and PHP support matrix, so do not assume compatibility from the package name alone. Check the package composer.json and README for the authoritative constraints. Also verify the goldnead/statamic-flow-canvas ^1.6.1 requirement against any pinned addon versions in your app.
- What Statamic events can trigger an automation?
- Automations can be triggered by content saves such as entries, Statamic form submissions, and schedules. The addon is designed for event-driven workflows around forms, entries, leads, and webhooks. The exact built-in trigger list should be confirmed against the version you install.
- Can I add my own custom triggers and actions?
- Yes, the addon supports custom triggers and actions so you can connect project-specific events and jobs to the visual flow builder. This is useful when built-in triggers do not cover your domain logic or when you need to call internal services. Review the extension points and test custom classes across your supported Statamic versions.
- What changes with the goldnead/statamic-flow-canvas 1.6.1 dependency?
- Version 1.6.1 moves canvas components from Tailwind utilities to plain CSS, which helps standalone installs but can affect custom canvas styling overrides. Confirm that your visual builder renders correctly after upgrading, especially if you shipped custom component classes. There is no data migration noted, but you should resolve any pinned addon constraints before deploying.
- How does the mail thumbnail renderer work and what does it require?
- The addon includes a server-side headless-Chromium renderer that photographs send_email mails for the Flow Canvas mail tile. It requires a Chromium binary and a writable thumbnail location in every environment where previews should render, not only where flows execute. The render timeout is configurable and defaults to 20 seconds in the evaluated release, so heavy mails may need adjustment. Confirm Chromium is patch-managed and sized for per-render CPU and memory use.
- Is the Chromium thumbnail renderer safe to run in production?
- The v2.29.1 fix materially reduces the prior risk of an unsandboxed browser loading arbitrary mail HTML. Residual risk remains because the sandbox is disabled automatically when running as root, which is common in containers, leaving HTML reduction, JavaScript-off, and a dead proxy as the effective controls. The own-host allow-list also permits same-host fetches during rendering, so document that surface and treat STATAMIC_AUTOMATIONS_NO_SANDBOX as a break-glass setting only.
- How should I configure thumbnail storage and cleanup?
- Thumbnails are written to a configured writable location, so verify whether you are using local disk, S3, or another driver and whether the delete-on-automation-delete path covers it. Deletion is irreversible, so check retention, audit, and export expectations before enabling it broadly. Also confirm automations.thumbnails.* settings survive config:cache and clean up pre-existing orphaned automations/thumbs/{uuid}/ directories. If assets live on a CDN or different host, test whether host-scoped allow-listing causes blank thumbnails.
- What are alternatives to goldnead/statamic-automations?
- Alternatives depend on whether you need Statamic-native visual automation or general workflow orchestration. Native Statamic form notifications and Laravel events, queues, and jobs can cover simpler cases, while external tools such as Zapier, Make, or n8n fit cross-system workflows. Choose this addon when you specifically want Control Panel-configured automations around Statamic content, forms, and webhooks.