FlowsBook a callSign inCreate free accountSign up
AI employees and automation

How to automate email reports: who gets them, what goes in, and the limits

A scheduled flow that gathers data, writes a short summary and emails it or attaches a PDF. Who may receive it, unsubscribes and the Free plan limits.

Part of the guide AI employees

By the xMap team · · 4 min read

To automate email reports, you need four blocks in a row: a Schedule that sets when, a data block that gathers what the report is about, an xMap LLM block set to The whole list that writes one summary of it, and an Email block (or Make a report, for a PDF attachment) that sends it. Built once in xMap Flows, the report arrives on time every day, week or month without anyone copying figures into a message.

Most of the work is not building the flow. It is deciding who receives the report, what one screen of it should say, and what happens when people stop wanting it. This article covers those decisions, with the rules the Email block follows.

The four blocks

  1. Schedule: every weekday at 7:30, every Monday at 8, or the first of the month. Set the time zone of the people reading it, not your own.
  2. A data block: Nearby places for businesses in an area, Traffic incidents for road closures, Job postings for companies hiring, My data for your own table, or Team findings for what your other AI employees found this week.
  3. xMap LLM with Work on set to The whole list. It reads every item and writes one text, called {{report}}. Tell it the length and the shape you want.
  4. Email, set to One email per run. The summary sits at the top, the list under it, and a link lets readers download every field as a CSV for 30 days.

Swap the Email for Make a report when readers want a document to forward or print: it attaches a PDF with your logo and color, the same summary, figures, charts, a map and the list.

Who gets it

The Email block takes up to ten addresses, separated by commas. Who those may be depends on your account:

Free planWith a plan or a credit pack
Who you can emailPeople at your own company's email domainsAnyone
Flow emails a day, for the whole organization50300
Sender shownYour organization, via xMap FlowsThe same, or your own domain once set up

From the Email block's rules. Replies go to the flow's owner.

So on the Free plan a report to your own team works at once, but one to a client or a personal address is refused before the flow goes live, with the reason in words.

Unsubscribes and bounces

Every email a flow sends has an unsubscribe link. Someone who uses it, an address that bounces, or one that reports the email as spam is skipped from then on, and the run's step says how many were skipped. You do not have to keep a list yourself, but you do have to accept the choice: if your sales director unsubscribes from the Monday report, the fix is a better report, not a new address for her.

Writing instructions for the summary

The summary is the part people read. A few lines of instruction make a big difference:

  • Say who reads it: for a regional manager with two minutes on Monday morning.
  • Say the shape: three bullet points of what changed, then one sentence on what to look at first.
  • Keep it to the data: use only the figures in the list; if something is not in the data, do not mention it.
  • Say what to leave out: no greetings, no sign-off, no advice.

A worked example (made up)

A delivery firm in Johannesburg has eight depots, and every Monday its operations coordinator used to search for roadworks and closures near each one before the planning call. She builds a flow from the Weekly road disruption report template: Schedule (Mondays at 6:45, Johannesburg time), Area of interest (the depots), Traffic incidents, xMap LLM on the whole list with the instruction group the closures by depot, nearest first, one line each, then Email to the six depot managers, all at the company's own domain.

The first Run once shows a long list for one depot near a stadium, so she adds a Filter to keep closures within 3 km of a depot. The next Monday the email arrives before the call, and the call is shorter.

Mistakes to avoid

  • Sending one long report to everyone. Make a second flow for the group that needs a different cut.
  • A daily report on something that changes weekly. People learn to ignore it.
  • Leaving the subject empty when several reports go to the same person. Give each a subject that says what it is.
  • Testing with a test run only. A test run shows what the email would contain but sends nothing; press Run once to see the real email in your inbox.

A scheduled report is the simplest kind of AI employee, and the workflow automation guide shows where it fits among the others. Templates such as the weekly brief from your AI employees are a quick start.

Questions

Can each person get their own version of the report?

Either make one flow per group with its own filter, or set the Email block to one email per item and put a field holding each item's address in To, for alerts rather than long lists.

What if there is nothing to report this week?

With no items to send, no email goes out. If you want a short 'nothing new' note instead, ask for it in a separate flow.

Can the report go to Slack instead of email?

Yes. Replace the Email block with the Slack app block and use {{report}} in the message.

Can I send the report from our own domain?

Yes, once your domain is set up under Settings, Email sender. Until then the sender shows your organization via xMap Flows.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.