Email

Overview

Free n8n workflow: Email. 15 nodes across emailReadImap, theHive, cortex, wait, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "Email", wires together emailReadImap, theHive, cortex, wait in 15 nodes. 15 nodes · emailReadImap, theHive, cortex, wait It starts from a manual trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

• Import "Email" into n8n, reconnect credentials for emailReadImap, theHive, cortex, wait, and run the same automation in your own workspace.
• Use it as a starting template when wiring emailReadImap, theHive, cortex, wait — adjust node parameters to your accounts and record IDs.
• Study how data moves from emailReadImap to theHive before building your own variant.
• Share it with your team as a documented reference for manual automations in the emailReadImap stack.

Example output

Imported into n8n, "Email" exposes 15 configured nodes. Trigger type: manual. Integrations: emailReadImap, theHive, cortex, wait. Open each node after import to map credentials to your own emailReadImap and theHive accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Frequently asked questions

How do I import "Email" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "Email" use?

It uses: emailReadImap, theHive, cortex, wait. The flow diagram above shows how each service connects across the 15 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own emailReadImap and theHive credentials in n8n after import.

What trigger type does "Email" use?

Trigger type: manual. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "Email" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for emailReadImap, theHive, cortex, wait.