Loading Karl Mercado portfolio.

Clear handoffs. Cut repetition.

I clarify administrative work, then automate repetitive steps without hiding the decisions that still need people.

View selected work Contact
Karl Mercado smiling in a cream embroidered shirt
Karl Mercado Administrative operations and AI automation I turn unclear requests, scattered tracking, and repetitive follow-up into systems people can understand and maintain.
Focus
Operational clarity
Tools
n8n, Make, Google Workspace
Location
Philippines, GMT+8

Automation is the final move, not the first.

I start with the operation underneath the tools: ownership, handoffs, status, exceptions, and the output that closes the loop.

Six questions keep a workflow legible.

Start with the request: what enters the operation, in what form, and with what information attached.

Working systems, shown clearly.

These independent portfolio builds use controlled or demo data unless noted. The contact workflow is live on this site. No client outcomes are implied.

Administrative operations with n8n

One operating flow for scattered requests.

Free-text requests are classified, scheduled, tracked, and summarized while exceptions remain visible for human follow-up.

Friction
Requests, schedules, and status changes live in separate places and require repeated checking.
System
Three connected workflows route requests, create calendar events, sync RSVP status, and prepare a daily brief.
Human result
Routine movement happens in the background while people keep control of decisions and exceptions.

Built with n8n, AI classification, Google Sheets, Google Calendar, Gmail

Proof
Public build documentation and three workflow outputs
Data
Controlled or demo records
Read the build documentation
Request management workflowClassifies and routes incoming work before scheduling or follow-up.n8n workflow
RSVP status syncMoves calendar responses into the shared tracker.Calendar to tracker
Daily operations briefTurns open work into a readable email summary.Gmail output

Support triage with n8n

A useful first pass for support requests.

Incoming messages become structured records, with urgent cases routed faster and the support team kept responsible for the response.

Support triage architectureValidates intake, structures the request, then separates urgent escalation from routine handling.n8n workflow
Friction
Messages arrive with different detail and urgency, so each one needs interpretation before it can move.
System
The workflow validates intake, structures the message, records the ticket, and routes urgent cases into faster channels.
Human result
Priority cases surface with context attached while the support person remains accountable for the customer response.

Demo disclosure: the HTTP handoff uses JSONPlaceholder as a mock endpoint, not a production ticketing API.

Proof
Workflow, urgent alert, and queue screenshots
Boundary
Controlled data with a mock ticketing handoff
Escalation outputProvides the urgent request and its context in one alert.Gmail
Structured queueKeeps urgent demo records visible for review and ownership.Airtable

Live qualification with Make

The contact form is also a working system.

Each inquiry is classified, recorded, and routed before Karl reviews it and replies personally.

Intake
The form collects a clear project type, contact details, and the current operational friction.
Routing
A Make scenario classifies intent and writes the inquiry to the matching Google Sheets path.
Follow-up
A Gmail alert prompts a personal response. There is no automated sales sequence.
Proof
Live site intake with routing and notification outputs
Protection
Turnstile verification before submission
Contact
Lead qualification workflowClassifies intent, routes the record, and prepares a follow-up alert.Make scenario
Tracking outputRecords the inquiry in the matching intent view.Google Sheets
Follow-up outputBrings the submitted context into a personal review.Gmail

Evidence without inflated claims.

This is an early portfolio. The systems are working builds, not decorative mockups, and are not presented as client outcomes.

Working systems
Three practical builds
Live implementation
Contact qualification on this site
Open documentation
Administrative request system on GitHub
Data treatment
Controlled or demo data, clearly disclosed

Clear enough to explain. Small enough to maintain.

The engagement follows the work itself: understand the operation, change only what earns its place, and leave a system people can inspect.

  1. Audit the real process

    Map where work enters, who touches it, which decisions repeat, and where the operation stalls.

    Output: a legible operating map

  2. Build the repeatable path

    Automate stable steps, connect the tools that matter, and keep exceptions visible.

    Output: a tested working flow

  3. Handover without mystery

    Test realistic cases, document decisions, and leave a system that can be checked and maintained.

    Output: documentation and handover

Bring me the messy version.

If a process depends on copying, chasing, sorting, or remembering, it is probably worth reviewing. You do not need a polished brief.

Emailkmhmercado@gmail.com LinkedInlinkedin.com/in/karl-mercado GitHubgithub.com/kmhmercado
0/3000

Complete the human check before sending. If it cannot load, you can still email me directly.

Your note enters the live intake workflow, then I review and reply personally. No mailing list or automated sales sequence.

Submissions pass through Cloudflare Turnstile and the disclosed inquiry workflow. Read how contact data is handled.