Stripe + Outlook: deliver files and log sales in Sheets

You get the “Payment successful” notification…and then the scramble starts. Find the right file, attach it, write the email, double-check the buyer’s address, then remember to log the sale somewhere you can actually reconcile later. It’s a lot of tiny steps, and tiny steps are where mistakes hide.

This Stripe Outlook automation hits automation creators first, honestly, because buyers expect instant delivery. But consultants selling templates and small teams running digital downloads feel the same pressure. The outcome is simple: buyers get the right file within minutes, and every sale is logged automatically in Google Sheets.

Below, you’ll see exactly how the workflow works, what it automates end-to-end, and where you can tweak it so it matches your product catalog and brand voice.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Stripe + Outlook: deliver files and log sales in Sheets

Click to explore

flowchart LR

    subgraph sg0["Stripe Event Flow"]
        direction LR
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/stripe.svg' width='40' height='40' /></div><br/>Stripe Event Trigger"]
        n2@{ icon: "mdi:cog", form: "rounded", label: "Remove Duplicate Items", pos: "b", h: 48 }
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Primary API Request"]
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/stripe.svg' width='40' height='40' /></div><br/>Stripe Charge Lookup"]
        n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Prepare Data Fields", pos: "b", h: 48 }
        n6@{ icon: "mdi:database", form: "rounded", label: "Append Sheet Records", pos: "b", h: 48 }
        n7@{ icon: "mdi:database", form: "rounded", label: "Get Sheet Rows", pos: "b", h: 48 }
        n8@{ icon: "mdi:cog", form: "rounded", label: "Run Sub-Workflow (Configure ..", pos: "b", h: 48 }
        n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Enrich Dataset", pos: "b", h: 48 }
        n10@{ icon: "mdi:cog", form: "rounded", label: "Drive File Save", pos: "b", h: 48 }
        n11@{ icon: "mdi:cog", form: "rounded", label: "Drive File Copy", pos: "b", h: 48 }
        n12@{ icon: "mdi:cog", form: "rounded", label: "Send Outlook Email", pos: "b", h: 48 }
        n13@{ icon: "mdi:cog", form: "rounded", label: "Outlook Notice", pos: "b", h: 48 }
        n14@{ icon: "mdi:cog", form: "rounded", label: "Outlook Followup", pos: "b", h: 48 }
        n2 --> n3
        n6 --> n7
        n9 --> n10
        n7 --> n8
        n4 --> n5
        n4 --> n13
        n5 --> n6
        n3 --> n4
        n3 --> n13
        n12 --> n14
        n10 --> n11
        n8 --> n9
        n8 --> n13
        n11 --> n12
        n1 --> n2
    end

    subgraph sg1["Flow 2"]
        direction LR
        n0@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Utility: Route by Criteria", pos: "b", h: 48 }
        n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/html.dark.svg' width='40' height='40' /></div><br/>Utility: HTML Render A"]
        n16["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/html.dark.svg' width='40' height='40' /></div><br/>Utility: HTML Render B"]
        n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/html.dark.svg' width='40' height='40' /></div><br/>Utility: HTML Render C"]
        n0 --> n15
        n0 --> n16
        n0 --> n17
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n1 trigger
    class n0 decision
    class n6,n7 database
    class n3 api
    classDef customIcon fill:none,stroke:none
    class n1,n3,n4,n15,n16,n17 customIcon

Why This Matters: Manual Delivery Breaks the Moment of Purchase

Digital products are supposed to feel instant. But when delivery depends on you noticing a Stripe payment, finding the correct file, and composing an email, “instant” turns into “when I get a minute.” Then the real mess starts: a buyer replies asking where the file is, you re-send it, you wonder if you attached the latest version, and you still haven’t updated your sales tracker. It’s mentally noisy work, and it ruins the clean, professional experience you’re trying to sell.

It adds up fast. Here’s where things usually go sideways.

You end up delivering late because notifications get buried in Slack, email, or Stripe dashboards.
A wrong or outdated attachment slips through, which creates refunds and support threads you didn’t plan for.
Sales logs don’t get updated consistently, so end-of-month reconciliation turns into detective work.
When you add a second product, the “quick manual process” becomes a mini-operations job.

What You’ll Build: Automatic Delivery + Sales Logging From Stripe

This workflow turns a Stripe payment into two things you can rely on: instant buyer delivery through Outlook and a clean sales record in Google Sheets. It starts the moment Stripe sends a paid event, then it checks for duplicates (so one purchase doesn’t accidentally send two emails). Next, it pulls the charge details from Stripe and uses an API request to fetch the right product information for that buyer. From there, it prepares the fields you care about, appends a row in Google Sheets, and can run a sub-workflow to enrich or standardize the dataset before delivery goes out. Finally, it saves and copies the file in Google Drive, renders a branded HTML email, then sends the buyer the correct attachment and sends you a separate notification.

The workflow begins with a Stripe event trigger and a quick “cleaning” pass to remove duplicate items. Then it enriches the order (API + Stripe lookup), logs the sale to Google Sheets, and prepares the buyer’s deliverable in Google Drive. The last stage is Outlook: one email to the customer with the file and instructions, plus internal notices/follow-ups so you know what sold.

What You’re Building

What Gets Automated

What You’ll Achieve

Stripe paid events trigger delivery without you checking dashboards.
Charge details are fetched and normalized into clean fields for tracking.
Each sale is appended to Google Sheets, then re-read for downstream logic.
Your delivery file is saved and copied in Google Drive before emailing.

Most sellers save about 2 hours a week once sales are steady.
Fewer missed attachments because delivery is consistent every time.
A reliable spreadsheet ledger you can hand to finance or import elsewhere.
A more “storefront-like” experience that reduces refund requests.
More room to scale from one template to a full catalog.

Expected Results

Say you sell 20 templates a week. Manually, you spend maybe 10 minutes per order pulling the file, attaching it, writing the email, and logging the sale, which is about 3 hours of admin. With this workflow, you do the initial setup once, and each new sale is basically hands-off: a Stripe trigger fires, Drive prepares the attachment, Outlook sends delivery, and Sheets logs it. Your time per order drops to “check the occasional support email,” not repetitive sending.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Stripe to capture payments and trigger events.
Microsoft Outlook to send branded delivery emails.
Google Sheets for a simple, searchable sales ledger.
Google Drive to store, copy, and attach deliverables.
Stripe API key (get it from Stripe Dashboard → Developers → API keys).

Skill level: Intermediate. You’ll connect accounts, map a few fields, and confirm Stripe event types.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A Stripe payment event kicks things off. When Stripe reports a successful purchase, n8n starts the workflow immediately. A quick duplicate-removal step helps prevent accidental double delivery if Stripe retries an event.

Order details are pulled and cleaned up. The workflow uses an HTTP request plus a Stripe charge lookup to gather the buyer’s email, product identifiers, and payment details you want to keep. Then a “prepare fields” step formats everything so it’s consistent (names, IDs, timestamps, and so on).

Sales tracking happens in Google Sheets. A new row is appended for every purchase, and the sheet is read back so the workflow can use the latest stored record for later steps. If you want custom logic (routing by product, tags, different email templates), a sub-workflow is designed to be plugged in here.

The deliverable is prepared in Google Drive, then sent via Outlook. The file is saved, copied (useful when you want a per-customer copy), and attached to a branded HTML email. Outlook also sends internal notices and follow-ups so you always know a sale happened, even if the buyer never replies.

You can easily modify the product-to-file mapping to support more templates, bundles, or client-specific versions based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Stripe Event Trigger

Set up the workflow entry point so new Stripe events start the automation.

Add and open Stripe Event Trigger.
Credential Required: Connect your Stripe credentials.
Select the Stripe event types you want to listen for in Stripe Event Trigger (e.g., payment/charge events).
Confirm Stripe Event Trigger is connected to Remove Duplicate Items.

⚠️ Common Pitfall: If Stripe credentials are missing, the webhook will fail to validate and no events will enter the workflow.

Step 2: Connect the Payment Data Retrieval Chain

Fetch raw payment details, look up Stripe charges, and structure the fields for downstream storage.

Open Remove Duplicate Items and define the fields used to identify duplicates (e.g., charge ID or event ID).
Configure Primary API Request with the API endpoint, method, and any headers needed for your primary data source.
Open Stripe Charge Lookup and map the charge identifier from Primary API Request.
Credential Required: Connect your Stripe credentials in Stripe Charge Lookup.
Use Prepare Data Fields to normalize the output fields for Google Sheets and email steps.

Tip: Primary API Request outputs to both Stripe Charge Lookup and Outlook Notice in parallel, so keep the response payload consistent for both paths.

Step 3: Connect Google Sheets Storage

Store processed payment records and read them back for enrichment.

Open Append Sheet Records and select the target spreadsheet and sheet tab.
Credential Required: Connect your Google Sheets credentials in Append Sheet Records.
Map fields from Prepare Data Fields to the sheet columns.
Open Get Sheet Rows to read the same sheet range needed for enrichment.
Credential Required: Connect your Google Sheets credentials in Get Sheet Rows.

⚠️ Common Pitfall: If the column names in Append Sheet Records do not match those expected by Get Sheet Rows, the enrichment step will produce empty values.

Step 4: Configure the Sub-Workflow and Enrichment

Run additional processing in a child workflow and enrich the dataset before saving files.

Open Run Sub-Workflow (Configure Required) and select the child workflow you want to execute.
Map the input data from Get Sheet Rows into the sub-workflow.
In Enrich Dataset, define additional fields or computed values based on the sub-workflow output.
Note that Run Sub-Workflow (Configure Required) outputs to both Enrich Dataset and Outlook Notice in parallel.

Tip: Keep the sub-workflow output schema consistent to avoid breaking field references in Enrich Dataset.

Step 5: Configure File Outputs and Outlook Emails

Save enriched data to Google Drive and send notification emails from Outlook.

Open Drive File Save and choose the destination folder and file naming pattern.
Credential Required: Connect your Google Drive credentials in Drive File Save.
Configure Drive File Copy to duplicate the saved file if needed.
Credential Required: Connect your Google Drive credentials in Drive File Copy.
Set up Send Outlook Email, Outlook Followup, and Outlook Notice with recipients, subjects, and body templates.
Credential Required: Connect your Microsoft Outlook credentials for Send Outlook Email, Outlook Followup, and Outlook Notice.
Confirm the sequence Drive File Save → Drive File Copy → Send Outlook Email → Outlook Followup.

Step 6: Configure HTML Utilities and Routing

Optional HTML rendering paths are available for templating or formatting content.

Open Utility: Route by Criteria and define your routing rules.
Configure HTML templates in Utility: HTML Render A, Utility: HTML Render B, and Utility: HTML Render C.
Confirm Utility: Route by Criteria outputs to Utility: HTML Render A, Utility: HTML Render B, and Utility: HTML Render C in parallel.

Step 7: Test and Activate Your Workflow

Validate each stage from Stripe event intake to storage and notifications before turning it on.

Click Execute Workflow and trigger a test Stripe event to start Stripe Event Trigger.
Verify that Remove Duplicate Items passes unique items to Primary API Request and Stripe Charge Lookup.
Confirm new rows appear via Append Sheet Records and that Get Sheet Rows returns data for Run Sub-Workflow (Configure Required).
Check that files are created through Drive File Save and Drive File Copy, and that emails send via Send Outlook Email and Outlook Followup.
When successful, switch the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Stripe credentials can expire or be restricted by environment. If things break, check Stripe Dashboard → Developers → API keys and confirm you’re using the right mode (test vs live) first.
If you’re using Wait-style timing in sub-workflows or relying on Drive file availability, processing times vary. Bump up any wait duration if downstream nodes fail on empty responses or missing file IDs.
Outlook HTML emails can look “off” if the rendered template is too generic. Add your brand voice and formatting early (header, footer, support contact), or you will be tweaking every message manually.

Quick Answers

What’s the setup time for this Stripe Outlook automation?

About 45 minutes if your Stripe, Outlook, and Google accounts are ready.

Is coding required for this Stripe Outlook automation?

No. You’ll connect Stripe, Outlook, Google Drive, and Google Sheets, then map a few fields.

Is n8n free to use for this Stripe Outlook automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google Workspace or Microsoft 365 costs (if applicable) and any Stripe fees you already pay per transaction.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this Stripe Outlook automation workflow for different use cases?

Yes, and you probably should. You can route different products to different email templates by editing the “Route by Criteria” logic and swapping which HTML Render node (A/B/C) is used. If you sell multiple files, change the Google Drive Save/Copy steps to select a different folder or filename based on the Stripe product ID. Common tweaks include adding a second internal notification recipient, sending a receipt PDF, or logging extra fields (coupon used, VAT ID, or refund status) to Google Sheets.

Why is my Stripe connection failing in this workflow?

Usually it’s the wrong API key (test mode vs live mode) or a rotated key that wasn’t updated in n8n. Double-check the credentials used in the Stripe Trigger and Stripe Charge Lookup nodes, then confirm the event type you’re listening for actually exists in your Stripe webhook settings. If it fails only during higher volume, rate limiting can also show up, so throttling or batching purchases may help.

What volume can this Stripe Outlook automation workflow process?

On self-hosted n8n there’s no fixed execution limit, and most small stores can run hundreds of orders a day as long as the server is healthy.

Is this Stripe Outlook automation better than using Zapier or Make?

Often, yes, because this flow has a few moving parts: deduping, API enrichment, conditional routing, file handling in Drive, and multiple Outlook sends. n8n tends to handle branching and multi-step logic without turning it into a pricing puzzle. You also get the option to self-host, which matters once you’re processing lots of orders. Zapier or Make can still be the right choice if you want the simplest possible two-step flow and you don’t care about custom HTML templates or sub-workflows. Talk to an automation expert if you’re not sure which fits.

Once this is live, sales stop creating admin work. The workflow delivers the file, logs the purchase, and keeps your storefront feeling instant.

Stripe + Outlook: deliver files and log sales in Sheets

How This Automation Works

n8n Workflow Template: Stripe + Outlook: deliver files and log sales in Sheets

Why This Matters: Manual Delivery Breaks the Moment of Purchase