Automations | Custory Changelog

We've added Automations so your team can stop manually chasing follow-up work every time something changes in a journey. Instead of noticing an update, opening other tools, writing the same handoff context again, and posting a status message by hand, you can define a workflow once and let Custory run it for you. [Open Automations →](https://app.usecustory.com/automations)

## What's New

**Scheduled automations** run on a set interval — hourly, daily, or weekly — for recurring rhythms like morning summaries, weekly review loops, or regular cleanup and follow-up.

**Event-based automations** trigger the moment something important happens: a Custory item is created or updated, a status changes, impact or effort crosses a threshold, or a GitHub pull request is opened or merged. Combined with scoped filters — by journey, item group, status, impact, effort, changed fields, or GitHub repository — these automations stay focused on changes that actually matter.

**Multi-step actions** let each automation chain follow-up actions together so one trigger can create momentum across tools. A single workflow can create a new Custory item, open a Jira, Linear, or GitHub issue, and send a Slack update to the team. For actions like creating items, tasks, or sending messages, AI-drafted payloads mean Custory can write clearer issue titles, better handoff descriptions, and more useful updates based on journey context.

**Visibility and control.** Review validation issues before an automation runs, see run history, run scheduled automations manually, pause workflows without deleting them, and reactivate them when the team is ready.

## Why it matters

The value of journey mapping isn't just seeing the problem — it's turning what you learn into action while the context is still fresh. Automations help your team do that consistently, so important insights don't get stuck in the map. They move into execution.

We've added Automations so your team can stop manually chasing follow-up work every time something changes in a journey. Instead of noticing an update, opening other tools, writing the same handoff context again, and posting a status message by hand, you can define a workflow once and let Custory run it for you. [Open Automations →](https://app.usecustory.com/automations)

## What's New

**Scheduled automations** run on a set interval — hourly, daily, or weekly — for recurring rhythms like morning summaries, weekly review loops, or regular cleanup and follow-up.

**Event-based automations** trigger the moment something important happens: a Custory item is created or updated, a status changes, impact or effort crosses a threshold, or a GitHub pull request is opened or merged. Combined with scoped filters — by journey, item group, status, impact, effort, changed fields, or GitHub repository — these automations stay focused on changes that actually matter.

**Multi-step actions** let each automation chain follow-up actions together so one trigger can create momentum across tools. A single workflow can create a new Custory item, open a Jira, Linear, or GitHub issue, and send a Slack update to the team. For actions like creating items, tasks, or sending messages, AI-drafted payloads mean Custory can write clearer issue titles, better handoff descriptions, and more useful updates based on journey context.

**Visibility and control.** Review validation issues before an automation runs, see run history, run scheduled automations manually, pause workflows without deleting them, and reactivate them when the team is ready.

## Why it matters

The value of journey mapping isn't just seeing the problem — it's turning what you learn into action while the context is still fresh. Automations help your team do that consistently, so important insights don't get stuck in the map. They move into execution.