Noah Carpiso · Metro Manila, PH
Available for work

automation lab

Three workflow designs for recurring remote-operations problems, mapped for n8n and Make. Each names the problem, the process, the safeguards, the output, and the time it returns. These are build-ready designs — say the word and I'll wire one up.

Inbound Lead Triage

Lead management · Workflow design

n8n / Make · Email · Discord · Sheets

Leads stop getting lost between inboxes

📥 Capture · email / DM / form
·
🏷️ Classify · keyword + source
·
🔀 Route to queue
·
⏰ Escalate if unread > 2h
Problem

Inbound leads land in three inboxes at once. Nobody owns the first reply, so response times drift and warm leads go cold.

Process

Every inbound message is captured once, scored by keyword and source, then routed to the right queue. Anything unread after two hours pings the owner directly.

Output · time saved

A single deduplicated lead list and a first response inside 2 hours. Roughly 45 minutes of manual triage removed per day.

n8n / Make Gmail + Discord webhooks Dedupe guard Quiet-hours rule Human review above threshold

Weekly Ops & Community Report

Reporting · data processing · Workflow design

n8n · Discord API · X API · Notion · Sheets

The Monday report builds itself

📊 Collect · joins, activity, clicks
·
🧩 Merge into weekly Notion page
·
📤 Publish email + Discord digest
·
🚩 Alert on failure / ±30% swing
Problem

Weekly numbers for partners and moderators were compiled by hand — three tools, two spreadsheets, and always someone waiting.

Process

A scheduled job collects the metrics, merges them into a standard template, and posts the digest. Failures at any source raise a flag instead of silently shipping a half-empty report.

Output · time saved

A consistent Monday-morning report with zero copying. Around two hours of manual compilation removed per week.

n8n schedule trigger Discord + X APIs Notion database Failure alerts Anomaly flag ±30%

Ticket → Knowledge Capture

Support · admin coordination · Workflow design

Discord · n8n · Airtable / Notion

Every solved ticket makes the next one faster

✅ Ticket closed
·
🗂️ Capture Q + A fields
·
👀 Human review gate
·
📚 Publish FAQ + canned reply
Problem

Moderators answered the same questions every week, and the good answers lived only in archive scrollback.

Process

Closing a ticket opens a two-field capture: question and answer. A reviewer approves it, the FAQ database updates, and the canned-reply list stays current.

Output · time saved

A searchable FAQ that compounds. Repeat-question handling time drops by roughly half once the base is seeded.

Discord modals n8n Airtable / Notion Human review gate Version history

Have a repetitive process that eats your team's week?

Describe it — I'll map the workflow, the safeguards, and the hours it returns before any build starts.

LinkedIn ↗