The IMAP Node does not collect the email, but only marks it as read. It has been working before on the same adress (Gmail), but that was a test adress. After switching to the adress I want to use in the future, it only has the behaviour described above. When I changed back to the adress I was using during the tests, it does also n ot work anymore. There are no executions shown in the n8n log and in the docker logs there are also no entries regarding this.
Information on your n8n setup
- n8n version: 1.98.2
- Database (default: SQLite): Postgres
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- **Running n8n via (Docker, npm, n8n cloud, desktop app):**local docker
- Operating system: Ubuntu
Please share your workflow
Verify that there are no other IMAP nodes connecting to the same account that could consume messages before your flow is activated. If so, consider closing or disabling the duplicates.
Duplicate the problematic workflow and disable the original to avoid possible corruption in the IMAP node definition. In many cases, the copy works without issues.
Avoid using IMAP with Gmail accounts, and instead use the native n8n “Gmail” node (via Google API), which offers greater reliability and doesn’t require an app password or enabling IMAP.
Thanks for the answer. As we are not using Gmail Workspace, it is not possible to use the native Gmail node. I tried another Email Provider which worked totally fine in the beginning but also stopped working now. I also get the same result, the mail is marked as read but the workflow is not running. I also tried to connect n8n with outlook over the outlook node, this did not work either as I do not have a https adress which could be used by n8n. At the moment, there is no imap node working at all!