Build Your First AI-Generated Workflow in 5 Minutes
Describe your automation in plain English. The AI generates the workflow. Refine it visually. Deploy in seconds.
The generator always works from the live list of triggers and actions across your Aeion OS modules—every module contributes its own actions automatically. The AI receives a comprehensive list including action names, descriptions, and configuration options.
Scores of 0.85+ are recommended for immediate production use. Scores between 0.6-0.84 benefit from reviewing suggestions and warnings. Scores below 0.6 should be heavily reviewed or regenerated with a more specific prompt.
Yes. If your provider is registered in the Aeion AI registry, it appears in the dropdown. If not, you can add it in Platform > AI Settings. The generator supports any provider that implements the AI adapter interface.
Apply them sequentially: `simplify` → `add_error_handling` → `add_logging`. Each refinement operates on the output of the previous, and a clear diff tracks what was added, modified, or removed at each step.
Yes. The 50+ built-in actions cover every module: CRM (contacts, deals, pipelines), Commerce (orders, payments, fulfillment), Helpdesk (tickets, routing, SLA), Connect (SMS, calls, broadcasts), Workspace (pages, databases, meetings), Finance (invoices, journal entries). Cross-module workflows are first-class citizens.
Blueprint ships 23 pre-built templates across categories (Sales, Marketing, HR, Finance, etc.). Browse by category, difficulty, or search by name/description. Click "Use Template" to copy it to your canvas. Templates include the full workflow definition, documentation, and recommended provider/model settings.
Event triggers (`type: "event"`) listen to Aeion OS events in real-time—e.g., `record.created`, `record.updated`, custom module events. Schedule triggers (`type: "schedule"`) use cron expressions for time-based execution—e.g., `"0 9 * * 1"` for Monday at 9 AM. Webhook triggers accept inbound HTTP POSTs. Manual triggers are one-click executions.
History is scoped per user within your organization. Each user keeps up to 50 records; once you'd exceed that, the oldest non-favorited record is deleted to make room for the new one. Favorited records are exempt from that cleanup — there's no separate age-based expiry.