Getting started with Automations

Automations is Turtini's native workflow engine — the if-this-then-that layer for the platform. Build a workflow visually, point it at a trigger (a Firestore write, a schedule, a webhook, or a manual button), and chain together action steps that the same modules and Wally already expose.

Why native:
A workflow doesn't have to swivel-chair through OAuth, hit a third-party rate limit, or shuttle data through someone else's servers. It runs inside your org, with the same Action Manifest every other surface (Wally, SDK, MCP, ChatGPT, webhook) uses — so the same set of actions is callable from a Slido-like trigger, a Wally chat, or a developer's script.

The /automations page:
• A list of every workflow in the org with status, last run, last 24h stats.
• Click any workflow to open the editor — trigger card on top, vertical canvas of step cards below.
• A Runs section shows the eight most-recent executions; click one to drill into the full step-by-step timeline (input, output, duration, errors, retries).

Drafting from a description:
Click Draft with Wally in the editor and describe the workflow in plain language ("when an opportunity is marked Closed-Won, send a thank-you email to the contact and create a task for the account owner to schedule a kickoff"). Wally returns a starter workflow — trigger configured, step list filled in — that you can review and save. Drafts start disabled; you enable them when you're ready.