Email attachment condition in Journeys

Business problem

Users cannot currently trigger Journey automations based on whether an incoming email contains an attachment, a condition that already exists in standard Rules. This forces customers to create complex workarounds using Labels to bridge Rules and Journeys, increasing maintenance effort and complicating the setup for routing documents like invoices or CVs.

Wished result

A native "Email contains attachment" condition should be added directly within Journeys. This would centralize automation logic, allowing users to build advanced workflows—such as specialized AI Agent processing or team-specific routing for documents—without relying on external Rule dependencies.