We expanded the flexibility of automation actions so teams can shape follow-through more precisely around how they already work. This update is especially useful for teams using Custory to connect journey changes with analytics and delivery tools.
What's New
PostHog actions can work across multiple event names. Teams are no longer limited to a single event when configuring relevant PostHog analytics checks.
Better Jira and Linear configuration. Automation actions for Jira and Linear now handle priority and workflow state targeting more cleanly, which gives teams more control over where follow-up work lands.
Clearer automation setup behavior. Validation and action summaries are more aligned with the actual configuration, which makes automations easier to understand before they run.
Why it matters
Automations are only useful when they can fit real operating workflows. These changes make it easier to connect journey signals to analytics checks, task creation, and delivery systems without forcing teams into a narrower setup than they actually need.