Skip to main content
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

1

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.
2

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.”
3

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
4

Activate

Enable the toggle to activate. The automation runs on its schedule and posts results back to your Spaces conversation.

​
Trigger types

​
Automation examples

​
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:
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.

​
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
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.