FAQs - Automations

📚 Guides & Best Practices
1

Automations FAQ

What are Automations?

Automations allow you to schedule recurring tasks—such as daily briefings, weekly reports, or research digests—that Rebel runs in the background without you needing to be present or prompt it manually,.

How do I create a new automation?

There are two ways to set one up:

  1. Ask naturally: Simply tell Rebel, “Run my morning briefing at 8 AM on weekdays” or “Check my inbox every hour.” Rebel understands natural language schedules.
  2. Use the Wizard: Go to the Automations tab in the sidebar, click to add a new automation, and follow the steps to select a workspace file and set a schedule,.

What are “Event Triggers”?

Instead of running at a specific time (like 9:00 AM), event triggers allow Rebel to run tasks whenever a specific action occurs. A common use case is “When a meeting transcript is ready,” which can automatically trigger a summary or update project documentation immediately after a call ends.

Where do I see the results?

Each automation run produces a conversation transcript. You can view these by clicking View transcript in the Automations tab history. By default, these sessions are hidden from your main conversation list to keep your sidebar clean, but you can toggle visibility if preferred.

What are “System Automations”?

Rebel comes with built-in automations that run automatically, such as Daily Wins & Learnings (which runs at 09:30 to summarize your progress) and Use Case Refresh. You can enable or disable these in the Automations panel, but you cannot delete them.

Why does my automation status say “Blocked”?

If a run status is “Blocked,” it means a tool required by the automation was prevented from running by your security settings. You may need to adjust your permissions or approve specific tools in Settings → Safety,.

Can I use variables in my automation files?

Yes. You can use placeholders like [LAST_EXECUTED_SUCCESS] in your markdown files. Rebel will replace this with the timestamp of the last successful run, which is useful for tasks like “Summarize emails received since the last run”.