Automations in Octonous start the same way everything else does: you describe what you want in plain text. The difference is that what you're describing happens more than once.
"Every time a deal is marked as closed won in Salesforce, create a Notion onboarding page for the client and notify the customer success manager on Slack." Octonous reads that, builds the automation, and shows you what it set up before anything runs.
Every automation has four parts you can review and edit:
When to run: the trigger (an event in one of your tools) or schedule (a set time, like every Monday morning) that Octonous inferred from your description.
Model: the AI model powering the automation. The default works well for most use cases, but you can swap it if needed.
Actions: what Octonous will do each time it runs.
Instructions: the logic it will follow, in plain text you can read and edit directly.
Unlike the chat, automations run unattended. Octonous won't ask for approval mid-run. That's why Preview mode exists before you go live.
Every run is logged in Execution history.