Administrative request management
Public build documentation for the n8n request, calendar, RSVP, tracking, and daily-brief workflows shown in the lead case study.
Review the GitHub documentationA transparent index of what supports this portfolio, what the screenshots represent, and where the claims deliberately stop.
Public build documentation for the n8n request, calendar, RSVP, tracking, and daily-brief workflows shown in the lead case study.
Review the GitHub documentationThe portfolio contact form is the live intake for the Make qualification workflow shown on the home page. Cloudflare Turnstile protects the public form before Karl reviews and replies to the inquiry personally.
Inspect the live contact formworkflow-admin-main.jpg: request classification, routing, scheduling, tracking, and email workflow.workflow-rsvp.jpg: Google Calendar RSVP status synchronization.daily-brief-email.jpg: generated daily administrative operations brief.support-triage-workflow.png: validation, AI analysis, urgency routing, and record creation.support-urgent-alert.png: high-priority demo escalation sent through Gmail.support-airtable.png: controlled demo records in the urgent support queue.lead-qualification-make.png: Make scenario for classification, routing, tracking, and notification.project-03-lead-tracker-google-sheets.png: High Intent inquiry record in Google Sheets.project-03-high-intent-gmail-alert.png: Gmail notification produced by the live workflow.These are independent working portfolio builds. They are not presented as client engagements, and no client outcomes, testimonials, benchmarks, or production datasets are implied.
Case-study screenshots use controlled or demo data unless the portfolio explicitly states otherwise. The support workflow's HTTP handoff uses JSONPlaceholder as a mock endpoint rather than a production ticketing API.
Karl's photograph and KM monogram are project identity assets. The dark-theme portrait is an AI-illustrated treatment derived from the supplied photograph and is identified that way wherever it appears.
Contact submissions are used to review and reply to inquiries. The submitted name, email address, selected starting point, and message pass through Cloudflare Turnstile and a Cloudflare Worker before the disclosed Make workflow routes them to Google Sheets and Gmail. They are not added to a mailing list or automated sales sequence.
For access, correction, or deletion requests related to a submitted inquiry, email kmhmercado@gmail.com from the address used in the form.
If a source, disclosure, or project description needs correction, email Karl with the page and the specific statement so it can be reviewed directly.