Newsletter Intake

Documentation

Newsletter intake lets you add useful links to a project simply by forwarding email newsletters into Digest Engine. This is one of the fastest ways to teach a project what matters in your space, especially if your team already follows competitor newsletters, industry briefings, analyst roundups, or curated niche digests.

Instead of manually copying links out of email, you can forward the whole newsletter and let Digest Engine extract the relevant content into your project.

Newsletter intake is especially useful when valuable stories are already being surfaced by trusted curators outside your organization.

Teams often use it to:

capture links from competitor newsletters
collect stories from industry analysts and reporters
pull in curated links from expert roundups
reduce manual copy-and-paste work during editorial review

Once forwarded, those links can appear in the same project content library as material from your other sources.

Finding Your Project Intake Address

Each project has its own intake address. That address is tied to the specific project, so forwarded newsletters go into the right editorial workspace instead of being mixed across teams or topics.

To find it:

Open the project you want to feed.
Go to the project settings or intake settings area.
Copy the project-specific newsletter intake address.

Use the correct address for the correct project. If your organization manages multiple newsletters or topic areas, this keeps content scoped to the right audience.

When you forward a newsletter, try to send the original message as cleanly as possible.

Best practices:

forward the original HTML email instead of pasting pieces into a new message
avoid heavily editing the message before forwarding it
keep the body intact so the system can detect the embedded links and surrounding context

In general, a straightforward forward works best. The more the original email structure is preserved, the easier it is for the system to identify the actual article links and ignore the surrounding noise.

What Happens After You Forward It

When the email reaches Digest Engine, the system processes it as an intake event for that project. It attempts to extract the links and turn them into content candidates for the project library.

Depending on your organization’s setup and whether the sender is already trusted, one of two things usually happens:

the email is processed right away
the email is held for sender confirmation before processing continues

First-Time Sender Confirmation

To protect your project from spam or accidental forwarding, the first email forwarded from a new sender address is usually placed into a confirmation flow.

If that happens, the sender receives an automated confirmation email with a link that must be opened before the sender becomes trusted.

This means:

the first forwarded newsletter from a new sender may not appear immediately
once the sender is confirmed, future forwards from that address should move through much more smoothly

If you are testing intake for the first time, expect this first confirmation step.

Understanding Allowlist Status

Sender trust is managed through an allowlist. A sender address typically moves through a small lifecycle:

Pending: The email was received, but the sender has not completed confirmation yet.
Confirmed: The sender is trusted and future forwarded newsletters from that address can be processed normally.
Expired: The confirmation window passed before the sender completed the required step, so that attempt is no longer active.

If a sender remains pending for too long, it usually means the confirmation email was missed, filtered, or never acted on.

Managing the Allowlist

Your organization may allow admins or project owners to manage trusted senders directly. In that area, they can typically:

review which sender addresses are already trusted
pre-approve or confirm expected senders
revoke a sender if an address should no longer be allowed to submit newsletters

This is especially helpful if your team uses a shared editorial inbox or if several people regularly forward newsletters into the same project.

If a forwarded newsletter does not show up in your project content after a reasonable wait, work through the basics first:

Confirm that you forwarded it to the correct project intake address.
Check whether the sender still needs to complete the confirmation step.
Wait a few minutes for processing if the system is actively ingesting the message.
Ask your project admin to review the allowlist and intake status.

If it still does not appear after that, escalate to your organization’s administrator or support contact so they can inspect the intake flow more closely.

Recommended Workflow

Teams usually get the best results when they treat newsletter intake as a regular input channel rather than a one-off experiment.

forward valuable newsletters consistently from the same trusted addresses
use project-specific intake addresses carefully
confirm new senders promptly
review imported content in Projects and Content
move strong items into the editorial workflow for Newsletter Drafts

Used well, newsletter intake becomes a simple way to turn outside curation into structured content for your own project.