DEV Community: SolutionsCraft

Sync New Stripe Customers to a Google Sheet with n8n

SolutionsCraft — Fri, 07 Aug 2026 11:00:00 +0000

If your "CRM" right now is remembering who paid you, this fixes that in about ten minutes with zero code. Every time someone becomes a Stripe customer, their details land in a Google Sheet automatically.

Before you start

You'll need an n8n instance (local or cloud — a free n8n Cloud trial is the fastest way to get one), a Stripe account, and a Google account with a Sheet ready to receive rows.

Disclosure: the n8n Cloud link above is an affiliate link — if you sign up through it, we may earn a commission at no extra cost to you. See our affiliate disclosure for details.

Step 1: Add the Stripe trigger

Create a new workflow and add a Stripe Trigger node. Connect your Stripe account (an API key from the Stripe dashboard), and set the event to customer.created. This fires the workflow the moment someone new signs up or makes a purchase.

Step 2: Map the fields you want

Add a Google Sheets node after the trigger, set the operation to Append Row , and point it at your sheet. Map the columns using the data Stripe already sent through:

Name: {{$json["name"]}}
Email: {{$json["email"]}}
Created: {{$json["created"]}}

n8n resolves these expressions against the trigger's output automatically — no transformation step needed for a simple case like this.

Step 3: Test it

Use Stripe's test mode to create a customer, then check the workflow's execution log in n8n. You'll see exactly what Stripe sent and what got written to the sheet — useful for catching a field name mismatch before it happens with a real customer.

Tip: Turn on the workflow's Active toggle before trusting it in production. A workflow that only runs when you manually execute it in the editor won't catch real Stripe events.

What's next

The same trigger works for a Slack notification — add a Slack node in parallel with the Google Sheets node and you'll get pinged the moment someone new signs up, no extra Stripe configuration required.

Automate Windows Server Health Checks with PowerShell and Email Alerts

SolutionsCraft — Fri, 07 Aug 2026 10:00:00 +0000

Checking server health by logging in and eyeballing Task Manager doesn't scale past one or two machines. This script checks disk space, memory, and a list of critical services, and only sends an email when something's actually wrong — not a daily "everything's fine" notification you'll learn to ignore within a week.

Before you start

You'll need PowerShell 5.1+ (built into Windows Server) and SMTP credentials for sending mail — an app password if you're using Microsoft 365 or Gmail, or your internal relay if you have one.

Step 1: Write the check

Each check appends to an $issues array only when something crosses a threshold. Nothing gets added when things are fine, which is what keeps the email quiet on a normal day.

# health-check.ps1
$diskThreshold = 15 # percent free
$memThreshold = 10 # percent free
$services = @("W3SVC", "MSSQLSERVER", "Spooler")

$issues = @()

Get-PSDrive -PSProvider FileSystem | ForEach-Object {
    $freePct = ($_.Free / ($_.Free + $_.Used)) * 100
    if ($freePct -lt $diskThreshold) {
        $issues += "Drive $($_.Name): $([math]::Round($freePct,1))% free"
    }
}

$os = Get-CimInstance Win32_OperatingSystem
$memPct = ($os.FreePhysicalMemory / $os.TotalVisibleMemorySize) * 100
if ($memPct -lt $memThreshold) {
    $issues += "Memory: $([math]::Round($memPct,1))% free"
}

foreach ($svc in $services) {
    $status = Get-Service -Name $svc -ErrorAction SilentlyContinue
    if (-not $status -or $status.Status -ne "Running") {
        $issues += "Service $svc is not running"
    }
}

Step 2: Only email when there's something to say

if ($issues.Count -gt 0) {
    Send-MailMessage -To "you@solutionscraft.com" -From "server-alerts@yourdomain.com" `
        -Subject "Server health check: $($issues.Count) issue(s)" `
        -Body ($issues -join "`n") `
        -SmtpServer "smtp.yourprovider.com" -Port 587 -UseSsl `
        -Credential (Get-StoredCredential -Target "smtp-alerts")
}

Tip: Don't hardcode the SMTP password in the script. Get-StoredCredential (from the CredentialManager module) pulls it from Windows Credential Manager instead, so the script stays safe to commit or share.

Step 3: Run it on a schedule

$action = New-ScheduledTaskAction -Execute "powershell.exe" `
    -Argument "-File C:\Scripts\health-check.ps1"
$trigger = New-ScheduledTaskTrigger -Daily -At 8am
Register-ScheduledTask -TaskName "ServerHealthCheck" -Action $action -Trigger $trigger

What's next

If you're monitoring more than a couple of servers, this is also a good candidate for an n8n Execute Command node instead of Task Scheduler — you get a run history and retry logic for free, the same tradeoff covered in the n8n workflow tutorial.

Automate Your First n8n Workflow in 15 Minutes

SolutionsCraft — Fri, 07 Aug 2026 09:00:00 +0000

If you're still copying files between folders by hand, this is the tutorial that stops that. We'll build a workflow that watches a directory and archives new files automatically — no code required to start, then we'll add a script node for the parts n8n can't do alone.

Before you start

You'll need a running n8n instance (local, or self-hosted on a cheap VPS) and about fifteen minutes. This walkthrough uses the desktop app, but the steps are identical in n8n Cloud — the fastest way to get one running if you don't already have an instance is a free n8n Cloud trial.

Disclosure: the n8n Cloud link above is an affiliate link — if you sign up through it, we may earn a commission at no extra cost to you. See our affiliate disclosure for details.

Step 1: Add a folder trigger

Create a new workflow and add a Local File Trigger node. Point it at the folder you want to watch, and set the trigger event to "file added." This node polls the folder on an interval and fires the workflow whenever something new shows up.

Step 2: Move the file

Add a Move Binary Data node after the trigger, pointed at an archive/ subfolder. At this point you already have a working automation — no script required.

Step 3: Add the parts n8n can't do alone

Sometimes you need logic that's easier to write than to wire together visually — renaming files based on content, computing a checksum, whatever your case needs. Drop in an Execute Command node and call a small script:

# watch-folder.py
import shutil, pathlib

def archive(path: str) -> None:
    shutil.move(path, "./archive/")

Tip: Run this as a scheduled n8n workflow rather than a cron job — you get retry logic and a visual run history for free, and it's one less thing running outside of something you can see.

Step 4: Test it

Drop a file into the watched folder and confirm it lands in archive/ within a few seconds. Check the n8n execution log — every run is recorded, with the exact input and output of each node, which makes debugging a lot faster than a bare cron job with no output.

What's next

From here, the natural extensions are a Slack or email notification when a file lands in the archive, and swapping the local trigger for an S3 or Google Drive trigger if your files don't live on the same machine as n8n. Both are covered in upcoming posts.