> ## Documentation Index > Fetch the complete documentation index at: https://docs.skarmy.ai/llms.txt > Use this file to discover all available pages before exploring further. # Automations > Work Skarmy does for you on a schedule — a morning note, an inbox catch-up, a weekly recap — with every result waiting for you, and nothing sent on its own. Automations are work Skarmy does for you on a schedule. Tell it once, pick a schedule, and it checks in when something needs you. ## Before you start You need an account — guests can look at the page but not create automations. The number you can have running at once depends on plan: **2 on Free, 10 on paid plans**, per company. ## Create one Two doors, same result: * **On the Automations page** — select **New automation**, describe the job, pick a schedule. * **By asking the coach** — say `every morning, tell me what needs me first` and the coach creates it for you. ### Starting points Four templates cover the common jobs: | Template | What it does | Default schedule | | -------------------- | ---------------------------------------------------------- | -------------------------------- | | **Morning note** | A short note each morning on what needs you first. | Every day at 8:00 AM | | **Inbox catch-up** | Checks the company inbox and drafts replies for your okay. | Every day at 9:00 AM and 3:00 PM | | **Weekly recap** | What moved this week, and what to focus on next. | Every Friday at 4:00 PM | | **Competitor watch** | A weekly look at what similar companies are doing. | Every Monday at 9:00 AM | ## Schedules An automation can run hourly (every 1–12 hours), daily, weekly, monthly (on days 1–28), or once — at most **4 times a day**. Times follow your timezone's wall clock. ## Notify or quiet Each automation is either **notify** — every result surfaces on your Home dashboard — or **quiet** — results wait in the run history. Failures surface either way, so a broken automation never fails silently. ## The one hard rule > Automations read your apps but never send or post from them on their own. An automation can read your Gmail, your calendar, your Stripe — but if the job ends in something that should be sent, it puts the draft in the result for you to send with one look. The inbox catch-up drafts replies; you approve each one. See [App permissions](/company/app-permissions). ## Manage them The list shows each automation with its schedule and state — `Paused`, `Paused after failing`, `Done`, or its next run. Open one to: * **Run now** — try it immediately. * **Pause** / **Resume**. * **Edit** the job or the schedule. * **Delete**, with a confirmation. * Read the full **run history**, each run expandable to its result. ## Limits | Limit | Value | | ------------------- | ---------------------------------------- | | Active automations | 2 on Free, 10 on paid plans, per company | | Runs per automation | 4 per day | | Scheduled runs | 60 per company per day | | Manual **Run now** | 10 per hour | Automation runs do not spend your build credits. ## Verify * **Run now** produces a result in the run history. * A notify automation's result appears on Home. * Pausing stops the next scheduled run. ## Troubleshooting | Problem | Fix | | -------------------------------- | ---------------------------------------------------------------------------------------------------------- | | `Paused after failing` | Open the run history to see what went wrong, fix the job's description or the app connection, then resume. | | An automation "did nothing" | Check whether it is quiet — its results are in the run history, not on Home. | | You expected it to send an email | By design it never sends. The draft is in the result — send it from the [Inbox](/company/inbox). | | You cannot create another | You are at your plan's limit. Pause or delete one, or upgrade. | ## Next Give automations something to read. Where drafted replies wait for your okay.