How to Automate an Intelligence Newsletter with Y2

Y2 can automate the recurring research behind an intelligence newsletter and deliver a completed report to your account email, an eligible Elite workspace audience, or your webhook. Sending to an external subscriber list requires a connector to your publishing platform.

Start with one topic and one reviewer. The goal is a useful issue whose claims readers can check. The intelligence briefings workflow explains how profiles, schedules, and delivery fit together; this guide focuses on turning that output into a newsletter.

Choose the recipient before configuring delivery

Free includes one community-profile subscription. It does not include your own custom research profile. Review pricing and workspace limits before setting up the flow.

1. Give the report an editorial assignment

Open InfoOps → My Profiles and create a custom profile. Name the audience, topic, geography, and decision the newsletter should help with. Follow the profile editor guide for the available research settings.

Here is an example topic for a weekly industry issue:

Track developments in industrial automation for US manufacturers. Summarize material product launches, deployments, and supply-chain changes. Link the original sources, include their dates, separate announcements from observed results, and explain what a plant operations manager should investigate next. Exclude consumer gadgets and duplicate coverage.

This is a suggested configuration, not a generated report or a claim about current events. Use a small set of known stories to check whether the first output fits the assignment.

2. Schedule research before the editorial deadline

Choose a weekly weekday and UTC time. A Monday 14:00 UTC schedule starts a report run at that cadence; it is not a promise that an email arrives at 14:00. Leave time for generation and review. The scheduling reference explains the available frequencies and how schedule changes affect active profiles.

Check the next run shown in My Profiles. Convert from your local time to UTC and revisit the setting when daylight saving time changes.

3. Review the first issue in your own inbox

Keep delivery set to Email Only while evaluating the report. Individual email goes to the current email on your Y2 account. There is no arbitrary recipient field on each profile. Eligible Elite workspaces can instead choose a workspace audience. Email delivery documentation explains recipient selection and troubleshooting.

Review at least these four things before using the material in a subscriber issue:

• Evidence: do the cited pages support the claims, and are they the original sources?
• Recency: are old events being presented as this week's developments?
• Relevance: would the intended reader make a better decision from each item?
• Editorial quality: what needs correction, context, or removal before publication?

Keep a record of corrections. Recurring irrelevant results usually call for a narrower topic.

4. Add branding when the content is useful

Pro and Elite include branding templates. Configure the supported logo, colors, terminology, and static content fields, then inspect a rendered email. Confirm that source links remain readable and that the issue's author and purpose are clear.

Branding a Y2 report does not create a subscriber database or configure your external sender. Your publishing platform continues to manage those parts of the newsletter.

5. Connect an external publishing platform

For an external audience, build a small connector using your publishing service's documented API. The Y2 side has three stages:

1. Configure an HTTPS endpoint under Developers → Webhooks and test it.
2. Assign that webhook in the profile's Delivery Preferences.
3. Receive the completion event, retrieve the full report, and create a draft in your publisher.

The webhook is a compact CloudEvents notification. It contains the report identity and API links; it does not embed the full report HTML or every source. Use the Reports API with the required scope to retrieve the content. Creating a new key requires Pro or Elite.

Follow the webhook delivery guide for signature verification, deduplication, and failure behavior. Accept the event durably before acknowledging it. The current delivery path does not run an independent automatic retry loop, and repeated failures can disable the webhook, so monitor the connector's delivery state.

Selecting Webhook replaces email and SMS for that subscription. There is no combined Email + Webhook setting. Have the connector create a reviewable draft, then publish it through your normal editorial process.

What should you measure?

Track the number of issues produced, editing minutes per issue, claims requiring correction, and delivery failures. In your publishing platform, measure reader engagement and whether subscribers find the coverage useful. A scheduled report alone does not establish newsletter ROI.

For the next step, compare plans and create one custom profile. If you are still choosing a research tool, compare Feedly alternatives for intelligence briefings or Y2 and Perigon against the same editorial assignment.