How to Build an Email Swipe File (and Feed It to AI)

A friend who runs email for a couple of brands described his team to me as "a machine for collecting good emails." Not sending them. Collecting them. Every time a subject line gets them to open, or a launch sequence is structured in a way they hadn't seen, someone saves it. Later, when they sit down to write, those emails go into the prompt as examples of what good looks like.

That's a swipe file. The idea is older than email. What's new is the second half: the file is now also AI context, and that changes what "saving an email" has to mean.

What a swipe file actually needs to do now

Copywriters used to keep swipe files in a drawer. Then it was a Gmail label, a Pinterest board, a folder of screenshots, or a browser tab with Really Good Emails open.

All of those are fine for looking. The moment you want to hand the collection to a model, they fall apart. A Gmail label lives inside Gmail and nowhere else. Screenshots don't have text in them, so you end up retyping subject lines into the prompt. Gallery sites are other people's picks, not yours, and they rarely have the ones from your niche.

What you want instead is each email saved as text, with its metadata next to it, in a place you can search and filter. Subject, sender, date, the full body with headings and links intact, and a couple of fields you added yourself: what kind of email it is, and why you kept it. From there you can filter to "win-back emails I rated highly" and paste the bodies into a prompt in ten seconds.

That's what I built Quicktion for, even if I didn't have swipe files in mind at the time. You forward an email to an address like abc123@in.quicktion.io and it lands in a Notion database, a Google Sheet, an Airtable table, or a Drive folder, with the fields already mapped.

Pick where the swipe file lives

This post covers four of Quicktion's six destinations. Linear and Trello are for turning emails into tasks, which isn't what a swipe file is. The other four split into two camps.

For the copy and structure, use Notion, Google Sheets or Airtable. The body arrives as markdown. Headings, bold text, bullet lists and links survive. Tracking pixels and invisible characters get stripped. It's the format you'd want to paste into a prompt anyway.

For the design, use Google Drive. Each email becomes a subfolder with email.pdf (the message rendered with its images, plus a header showing sender, date and subject), email.html (the original), and any attachments. If what you're collecting is layout, color, hero images and button placement, the PDF is the thing to keep. You can also upload a PDF straight into Claude or ChatGPT and ask about it.

I'd pick Notion if you're mostly reading and writing from the swipe file yourself. Sheets if you want to sort and filter across hundreds of rows, or share it with someone who won't open Notion. Airtable if you want a gallery view by brand. Drive if design matters as much as words. Nothing stops you from running two: one for copy, one for design, on separate forwarding addresses.

Set it up

1. Create the database

In Notion, a database with these properties works well. Quicktion fills the first five on its own. The last three are yours.

The same shape works as columns in a Sheet or fields in an Airtable table. In Sheets, Quicktion reads your header row and auto-matches columns named Subject, Date, Body and Email URL; anything it doesn't recognize you pick from a dropdown.

The "Why I saved it" field matters more than it looks. Six months from now you won't remember whether you kept an email for the subject line or the P.S. And when you hand the file to a model, that one line is the difference between "here are 20 emails" and "here are 20 emails, and this is what's good about each." The second prompt gets much better output.

2. Create the destination

In the Quicktion dashboard, create a destination and connect it to the database, sheet, table or folder. Quicktion maps the standard email fields by name, you confirm, and you get a forwarding address.

On a Drive destination there's no mapping at all, just the folder and a naming pattern. {date}_{subject} is the default. {sender} is handy for a swipe file, because {sender}_{date}_{subject} groups each brand's emails together when you sort by name.

3. Forward the good ones

Two ways to get emails in, and you can mix them.

Forward from anywhere. Open the email in whatever client you read it in, forward it to your Quicktion address, done. This is the one to use from a phone, from Outlook, from Apple Mail, or from the personal inbox where you're subscribed to forty brands. If you forward a newsletter that someone else originally received, Quicktion saves the original sender, not you, so the From field still says the brand.

Or save from Gmail with one click. The Gmail add-on adds a save button to the sidebar. Before it saves, you can edit any field, which is where you'd set Email type and type the "why" note. I do it this way for the emails I already know I want to keep, and forward for the ones I find on a phone.

Keep it curated. A swipe file of everything is an inbox. The free plan's 25 emails a month is roughly one a day, which is about the rate at which anyone actually sees an email worth keeping.

If you'd rather capture everything from a set of brands and curate later, there's a trick: subscribe to their lists with a plus-address like you+swipe@gmail.com, then set one Gmail filter for to:you+swipe@gmail.com that forwards to your Quicktion address. Every email from those brands files itself and you star the good ones in Notion. That burns through 25 a month fast, so it's a Pro workflow. The Gmail rules guide has more on filter setups.

4. Let the AI do the tagging (Pro)

AI Email Intelligence runs per destination. You pick the properties you want filled and describe them once, in plain language. For a swipe file, the extraction prompt looks something like:

Brand: the company sending this, from the signature or footer, not the ESP.
Email type: one of welcome, launch, win-back, cart abandonment, promo, newsletter, post-purchase.
Hook: the first line or the main idea of the opening, in the email's own words.
CTA: the text of the main button or link.

Every saved email comes in with those fields filled, so you only write the "why" line yourself. There's also a body prompt if you want the saved text cleaned up: "remove the footer, unsubscribe links and legal text" is a good one for marketing emails, because that stuff pads every prompt you paste the body into.

You can review what the AI filled in before it saves from the Gmail add-on, or just let forwards go through. The AI extraction guide covers the prompt side in more depth.

Feed it to the AI

This is the part that makes the file worth keeping. Three ways, roughly in order of effort.

Paste. Filter your database to what you need (say, Email type is win-back, saved in the last year), open a few pages, copy the bodies. Your prompt ends up looking like:

Here are 6 win-back emails I saved because of [what your "why" notes say].
Study the structure: how they open, how long the body is, where the
offer lands, how the CTA is phrased.

[email 1]
[email 2]
...

Write a win-back email for [product] aimed at customers who haven't
bought in 90 days. Same structure, our voice, no copying of phrases.

Six to ten examples is the sweet spot. Fewer and the model ignores them, more and it averages them into mush.

Connect. Claude and ChatGPT both connect to Notion and Google Drive. Once the swipe file lives in one of those, you can say "look at my Swipe file database, find the five best-performing subject line patterns across the launch emails, and write ten for X" and the model reads the pages itself. No copying. This is where the tagging fields pay off, because the model can filter the way you would.

Export. Notion exports any database to markdown or CSV. A Sheet exports to CSV. Either can go into a project as a knowledge file, so every conversation starts with your swipe file already loaded. I'd refresh it monthly.

For Drive, upload the PDFs directly or point a connected model at the folder. Asking "what do these eight emails have in common about how they lay out the hero section" against PDFs works better than you'd expect.

A few things I've learned

Save the whole email, not the subject line. The subject line is what made you open it, but the structure underneath is what you'll actually reuse, and you can't reconstruct it later.

Rate as you save. A 1 to 3 score in a Select field takes two seconds at save time and is impossible to do honestly in bulk afterwards. When you build a prompt you'll only want the 3s.

Keep sender-level notes somewhere. If one brand consistently sends good stuff, a Brand page in Notion with a rollup of their emails is a swipe file inside the swipe file.

Don't over-tag. Brand, type, a score and a why line is plenty. Every property beyond that is a property you'll stop filling in by week three.

Get started

Sign up, create a destination on the Notion, Google Sheets, Airtable or Google Drive page, and forward the next email that makes you think "that's good." Ten minutes, and the next time you sit down to write a campaign you'll have examples that are yours instead of whatever the model remembers from the internet.

If the newsletters you subscribe to are the raw material, the newsletter archive guide covers the automatic, save-everything version of this setup.