Messaging & email · One purpose, multiple implementations
email read imap
Adapt the published “email read imap” workflow to other implementations while preserving its documented behavior.
The source contains 1 executable node and 0 connections. This draft is derived from the n8n export; it needs a human-reviewed purpose, input/output contract, and behavioral tests before a port can claim equivalence.
Open agent files on GitHub ↗Shared workflow
This initial Mermaid diagram shows observed connections from the n8n source, including model and tool dependencies. Unresolved connections are listed under Evidence. It is a starting point for the shared design; it does not execute the agent or establish correctness.
Rendering the workflow diagram…
Read the Mermaid source
flowchart LR n0["IMAP Email"]
Implementations
Each implementation shares the agent’s purpose. Available source, planned ports, and verified results are labeled separately.
n8n
Source available · not runtime-tested
Read setup and source ↗Inspect the n8n canvas and download JSON →Build or operate with an assistant
Each prompt includes separate build and operating instructions tailored to this agent. They are untested instructions, not working implementations. Check the chosen product’s actual capabilities before using it.
Evidence and remaining work
The bulk collection has publication checks, not live-service testing. Diagrams and prompts are documentation. A port needs reviewed schemas, fixtures, actual execution results, and explicit limits before claiming equivalent behavior.
- Define input/output schemas and expected outputs.
- Review source expressions, external actions, and failure behavior.
- Determine whether model judgment is required or deterministic rules suffice.
Curated by Nik Bear Brown. Preserve each implementation’s original attribution and license. These source templates are separate from the audited Claude directory.