hey @Deni03, thanks for laying this out. You’re not missing a hidden settings screen for most of this (Linear triggers in Automations) are still fairly narrow.
Today the Linear triggers are Issue created, Status changed, and End of cycle, scoped mainly by team/project in the trigger UI, not status or priority pickers. If you need “only these triage statuses / priorities,” the practical workarounds are Linear-side triage rules on the project (Linear integration → Triage rules), or a Status changed trigger plus a prompt rule to exit when status/priority doesn’t match (it’ll still consume a run, same pattern as multi-project setups in this thread).
For PostHog there’s no native trigger yet, use a Webhook automation (PostHog CDP Destination → POST to the automation URL; payload lands at the bottom of your prompt) or enable PostHog MCP as a tool on a repo-less automation. (attach screenshot: trigger = Webhook, Tools = MCP server)
On the default-prompt integration warnings: those usually mean the prompt references a Tool that isn’t enabled or connected (e.g. PR title instructions need Open pull request plus GitHub + a repo on the automation), not a separate missing automation.
Can you share a screenshot of your trigger config and one warning line? Also confirm Linear + GitHub under dashboard → Integrations and whether the automation is Team Owned vs private.
Hope that helps, reply with those screenshots and we can pin down the exact warning.