Skip to content
Changelog

Report a bug

Automations Overview

Automations let AI start work without a person manually opening a thread. They can be scheduled or triggered by external events.

Create and manage them in Space settings → Automations. Every automation sends its work to the Space’s Threads area or a named channel.

TriggerUse for
ScheduleDaily reports, weekly reviews, recurring sweeps, timed reminders.
WebhookEvents from any service that can send HTTP requests, such as Sentry or a custom system.
App eventNative events from connected apps such as Slack, GitHub, or Linear.
RSS feedMonitoring new articles, changelogs, posts, or public feeds.
EmailStarting work by sending email to the Space’s generated address.
SlackLetting AI respond to relevant messages in a connected Slack channel.

When you create a webhook automation, Type gives you a URL and optional secret. Send a first event from the external service so Type can learn the event shape and render future events clearly in the workspace.

Good webhook instructions answer:

  • What service sends the event?
  • Which event types matter?
  • How should the event be summarized for humans?
  • When should AI act, and when should it only notify?

Slack setup has three parts:

  1. Connect Slack globally in Type.
  2. Invite the Type app into the Slack channel, or use the relevant slash command in Slack.
  3. In Space settings → Automations, select Slack, choose the Slack channel and Type destination, then decide when AI should respond.

Each Space has an inbound email address. Send email there when an external person or system should start a thread.

A template prompt can propose automations such as a daily user health report, weekly pipeline review, morning support digest, or weekly marketing ideas. These are suggestions, not automations that already exist. During setup, confirm the trigger or cadence, timezone, destination, and enabled state. A new automation stays disabled unless you explicitly ask for autonomous execution to begin.