> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finkkle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations in Finkkle Spaces: Scheduled and Event-Triggered Tasks

> Finkkle Spaces automations let you describe a recurring task in plain language and have it run on a schedule or trigger — without writing code or setting up external services.

Spaces automations turn a plain-language instruction into a task that runs automatically — on a schedule, when an event occurs, or on demand. Igno — Spaces' built-in AI agent — is a powerful automation and organization tool that handles everything from creating and configuring automations to tracking results and keeping your work organized across conversations.

## How automations work

You describe what you want to happen in a conversation:

> *"Remind me every weekday at 9 AM to review my open tasks."*
> *"After each meeting, summarize the conversation and create a follow-up checklist."*

Spaces parses the instruction, identifies the trigger (time-based or event-based), and creates the automation. You can review the configuration before activating it.

## Creating an automation

<Steps>
  <Step title="Open the Automations panel">
    In the Spaces left sidebar, click **Automation**. Or just describe the automation in any conversation — Igno will offer to create it.
  </Step>

  <Step title="Describe the task">
    Write the automation in plain language. Be specific about the trigger, what should happen, and what output you expect:

    > *"Every Monday morning, search for the latest news about AI regulations and send me a summary."*
  </Step>

  <Step title="Review the configuration">
    Spaces shows you the parsed automation:

    * **Trigger** — time schedule or event type
    * **Action** — what the automation will do
    * **Output** — where results are posted (conversation, notification, artifact)
    * **External actions** — if the automation will interact with outside services, you approve this explicitly
  </Step>

  <Step title="Activate">
    Enable the toggle to activate. The automation runs on its schedule and posts results back to your Spaces conversation.
  </Step>
</Steps>

## Trigger types

| Trigger         | Example                                                          |
| --------------- | ---------------------------------------------------------------- |
| **Scheduled**   | Every night at 02:00 UTC, every Monday, once on a specific date  |
| **Event-based** | On file upload, on form submission, on a connected service event |
| **Manual**      | Run on demand with a single click                                |

## Automation examples

| Automation            | What it does                                                                                       |
| --------------------- | -------------------------------------------------------------------------------------------------- |
| **Daily briefing**    | Every morning, searches for updates on a topic you follow and posts a summary to your conversation |
| **Weekly digest**     | Every Friday, compiles highlights from the week's conversations and outputs a structured recap     |
| **Meeting follow-up** | After you paste in meeting notes, generates a summary and a follow-up checklist automatically      |
| **Research alert**    | On a set schedule, monitors a topic area and flags new developments worth reviewing                |

## External action policies

When an automation needs to interact with an external service — sending a message, writing to a database, calling an API — Spaces uses one of three policies:

| Policy           | Behavior                                                             |
| ---------------- | -------------------------------------------------------------------- |
| **Observe only** | Reads data, reports results, takes no action                         |
| **Draft only**   | Prepares an output for your review before sending                    |
| **Auto-approve** | Executes the action immediately (use only when you trust the output) |

<Warning>
  Start with **observe-only** or **draft-only** policies for any automation that touches external systems. Switch to auto-approve only after you have reviewed several successful runs.
</Warning>

## Managing automations

* **View history** — each automation keeps a run log with timestamps and outputs
* **Pause / resume** — use the toggle to pause without deleting
* **Edit** — describe a change in plain language: *"Change the daily backup to run at 3 AM UTC instead"*
* **Delete** — removes the automation and its future runs; existing run history in conversations is preserved

<Tip>
  Use automations to reduce repetitive work — daily briefings, weekly summaries, monitoring alerts, and backup jobs are great starting points. Keep external-action automations in draft mode until you are confident in the output quality.
</Tip>