v1.1.41

Repository and Journey Automations

Automations can now work across repository and journey scope with richer context for AI, GitHub, Jira, and Linear workflows.

Custory automations got a meaningful upgrade in scope and capability.

Automations can now work in both journey and repository mode, which makes it easier to automate reusable blocks as well as individual journey work. The automation runtime and editor were updated to understand more context, better target steps, and handle more integration-driven workflows.

What's New

Repository-scoped automations. Automations are no longer limited to a single journey context. They can now operate on reusable repository content as well.

Smarter targeting. The runtime has better journey and step resolution, which makes it easier to direct actions at the right place in the workflow.

Broader integration actions. GitHub, Jira, and Linear workflows now have richer handling and more complete context when automations create or update work.

Better AI-assisted execution. Custory AI can use the richer repository and journey context when it runs automation-related actions.

Why it matters

This makes automations more useful once teams start reusing content across multiple journeys.

Instead of automating only a single map, teams can now build workflows around the reusable blocks and the journey-specific work that depends on them.