Get AI summaries of any video or article — Sign up free
How to forward email threads into your Reflect notes thumbnail

How to forward email threads into your Reflect notes

Reflect Notes·
5 min read

Based on Reflect Notes's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use Zapier’s “Email by Zap” trigger (“New inbound email”) to catch forwarded emails sent to a unique address.

Briefing

Star-based email saving works for single messages, but it breaks down when the goal is to capture an entire conversation. The workaround is a Zapier setup that creates a unique forwarding address; sending any email thread to that address automatically generates a new Reflect note containing the full nested thread, keeping daily notes clean.

The process starts in Zapier by creating a new Zap with the trigger set to “Email by Zap” and choosing “New inbound email.” The key step is defining a unique email address—something memorable but distinct—so that only forwarded messages meant for Reflect land in the workflow. The transcript emphasizes copying and storing the unique address because the “zapiermail.com” appendage is easy to forget.

To verify the trigger, the user forwards the latest email from a test thread to the unique address. Because email delivery isn’t instantaneous, Zapier may take a few seconds to detect the inbound message; the workflow may also offer a choice of which email to use if multiple messages were forwarded. Once the trigger successfully finds an email, the Zap is connected to Reflect with an action that creates a new note.

Instead of appending content to a daily note like a to-do item, the Reflect action is configured to create a standalone note for the forwarded thread. The note’s subject can be set to the email subject (the transcript suggests options like “email subject”), and the note can be configured not to be pinned by default. For the note body, the setup uses the email’s actual content—specifically the email body in Markdown—so the resulting Reflect note reads like an email.

A critical configuration detail is the Reflect graph ID, which identifies the correct Reflect workspace. After filling in the graph ID and running a test, the workflow confirms that a note was sent to Reflect. Checking Reflect shows the note does not appear in the daily note feed; instead, it appears under “All notes,” where it sits at the top and preserves the entire thread.

The payoff is practical: the note includes the full conversation, nesting all messages in the thread. That means long email chains—10, 15, or even 20 messages—can be captured in one place without manually copying and pasting. Just as important, the forwarding address can be used from any sender account. Once the unique Zapier forwarding address is set up, the same integration can receive threads forwarded from both personal and work email accounts, so the Reflect capture workflow only needs to be configured once.

Cornell Notes

A Zapier workflow can forward any email thread to a unique address, then automatically create a new Reflect note containing the entire nested conversation. The setup uses Zapier’s “Email by Zap” trigger (“New inbound email”) with a custom unique forwarding address, then connects it to a Reflect action that creates a standalone note (not a daily-note append). The note can be configured with the email subject and the email body content, and it requires the correct Reflect graph ID. Because email delivery can lag, testing may take a few extra seconds. Once configured, the same forwarding address works from multiple email accounts, letting users capture long threads in one clean note.

How does the Zapier trigger decide which emails should become Reflect notes?

It listens for “New inbound email” using Zapier’s “Email by Zap.” The workflow only triggers when an email is forwarded to the unique Zapier forwarding address created in the trigger step (the transcript uses a custom prefix like “sam reflect” plus the “zapiermail.com” domain). Forwarding the latest message from a thread to that address is what causes Zapier to detect the email and proceed.

Why does the setup create a new Reflect note instead of appending to a daily note?

The transcript contrasts two approaches: starring emails for daily-note append (useful for single to-do items) versus forwarding whole threads. For threads, appending every message to the daily note would clutter it. The Reflect action is therefore configured to “create a note,” producing a standalone entry under “All notes,” keeping daily notes focused.

What fields are used to shape what appears inside the Reflect note?

The note subject is set to the email subject (with the transcript mentioning “email subject” as the choice). The setup also sets “pinned” to false, so forwarded items aren’t automatically pinned. For the note body, it uses the email’s body content—entered as “note content HTML” is skipped, and the email body is placed into “markdown” (the transcript uses the “body plain” content).

What’s the role of the Reflect graph ID in the workflow?

The graph ID tells Zapier which Reflect workspace to write into. During configuration, the user double-checks the graph ID value and inputs it into the Reflect action. Without the correct graph ID, the note wouldn’t land in the intended Reflect account/workspace.

Why might Zapier testing take longer than expected?

Email delivery isn’t instantaneous. The transcript notes that the trigger test can take a few seconds because the forwarded email takes time to arrive and be detected. If multiple emails were forwarded to the unique address, Zapier may also offer a selection of which one to use for the test.

How can one integration capture threads from both work and personal email accounts?

The unique forwarding address is the only required destination. After the Zapier integration is set up once, the user can forward threads from any email account to that same unique address. The workflow then creates the Reflect note regardless of whether the original sender was personal or work.

Review Questions

  1. What unique element in Zapier must be created and saved to ensure only intended emails trigger Reflect note creation?
  2. Which Reflect action choice prevents long email threads from cluttering daily notes, and where do resulting notes appear?
  3. What configuration inputs determine the content and destination of the Reflect note (e.g., subject/body fields and graph ID)?

Key Points

  1. 1

    Use Zapier’s “Email by Zap” trigger (“New inbound email”) to catch forwarded emails sent to a unique address.

  2. 2

    Create and store a memorable unique forwarding address; the “zapiermail.com” suffix is easy to forget.

  3. 3

    Forward the latest email from an email thread to the unique address so the full thread can be captured as one note.

  4. 4

    Configure the Reflect step to create a standalone note (not append to a daily note) to avoid clutter.

  5. 5

    Set the note subject from the email subject and populate the note body with the email body content in Markdown.

  6. 6

    Include the correct Reflect graph ID so notes are written to the intended Reflect workspace.

  7. 7

    Expect a few seconds of delay during testing because email delivery can lag.

Highlights

A single Zapier forwarding address can turn any email thread into one Reflect note with nested messages.
Choosing “create a note” keeps threads out of daily notes, avoiding a to-do-list style pileup.
The workflow can accept forwards from both personal and work email accounts without reconfiguring anything.

Topics