I build the automations, integrations and data plumbing that small businesses and agencies run on, and I move data between systems without losing it on the way. Most of what I am handed is the unglamorous kind of work: an export where the same person appears three times under three spellings, a file estate that has to survive a migration exactly as it was, a workflow that stopped firing last Tuesday and nobody knows why.

200+ completed freelance engagements · 10+ years of client work · Google Workspace · Workflow automation · Mianwali, Pakistan (UTC+5)

⚙️ Workflow Automation — n8n Make Zapier Multi-app workflows, scheduled processing, operational automation and the integrations between tools that have no native connection.

📄 Google Workspace Systems — Apps Script Sheets Gmail Drive Contacts Forms Internal tools a team actually uses: scripted spreadsheets, generated forms, mailbox structure, and the Workspace troubleshooting nobody else wants.

🔌 API & Data Integration — REST APIs Webhooks JSON Data mapping Connecting two systems that were never designed to talk to each other, including the authentication and the failure behaviour.

🧹 Data Sync & Quality — Deduplication Reconciliation Cleanup Contact and CRM exports matched, merged and kept in step — with every conflicting value reported rather than quietly dropped.

☁️ Cloud Migration — Google Drive OneDrive Dropbox Mega File estates moved between providers with the folder structure and names intact, and verified afterwards rather than assumed.

🗂️ Client Operations Systems — Jotform Intake CRM workflows File architecture The form work arrives through, where it goes next, and the structure that keeps it findable six months later.

The strongest eight. The full index — 19 repositories, organised by discipline — is in automation-portfolio.

The part clients actually pay for is not the workflow. It is that the workflow does not quietly corrupt something at 3am on a Sunday.

1. Understand source and destination before touching either.
2. Define the source of truth — one system wins, in writing, before the first run.
3. Map the fields. Most integration failures are a mapping assumption, not a bug.
4. Handle duplicates deliberately. A merge rule decided up front beats a cleanup later.
5. Validate inputs rather than trusting that they arrive in the shape they did last month.
6. Test with controlled data, not the client's live records.
7. Verify the result — count it, compare it, don't assume the tool told the truth.
8. Handle the exceptions — and where something is genuinely ambiguous, stop and ask rather than guess.
9. Document the handover so it survives without me.

On larger builds this extends to retries, idempotent reruns, logging, alerting, a human approval step and end-of-run reconciliation — where the engagement warranted it. I do not claim every historical project had all nine.

Two distinct tracks, and they should not be blurred together:

2003 – 2023 · Technical, operations and training career Around twenty years of structured technical, administrative, operations, supervision and training work, beginning in Pakistan Air Force service. Documentation discipline, controlled operational environments, fault-finding, and training other people to follow a process correctly.

2015 – present · International freelance client services Remote delivery for clients in the UK, US, Europe and Australia through Fiverr and Upwork — 200+ completed engagements.

Recent specialisation Automation, integrations, Google Workspace systems, data migration and AI-assisted workflows.

That first track is not software engineering, and I do not present it as such. What it gave me is the habit of writing things down before touching them — which is most of why migrations I run do not lose files.

2003 ──────────────────────────────── 2023
   Technical / operations / training career
                  │
   2015 ──────────────────────────────▶ present
      International freelance client services
                                        │
                              Automation · Integrations
                              Google Workspace · APIs
                              Data migration · MCP tooling

The fifteen I am actually hired for:

n8n · Make.com · Zapier · Google Apps Script · Google Workspace · Google Sheets · REST APIs · Webhooks · Data migration · Deduplication & reconciliation · Airtable · Node.js · JavaScript · CSV / data cleanup · Model Context Protocol (MCP)

From the technical operations career, and useful rather than headline:

technical training · operations supervision · documentation discipline · quality and compliance awareness · fault-finding · preventive maintenance · administrative systems

This is operations and documentation discipline, not software engineering, and it is not presented as such anywhere in this portfolio.

Based on the reviewed Fiverr history snapshot of 26 September 2026 — not a lifetime total.

103 of 221 completed Fiverr orders were individually reviewed before the platform presented a human-verification step and the audit stopped. Every rating observed across those 103 was 5 stars. The remaining 118 completed orders are counted in the 221 total but were not individually reconstructed, and nothing has been estimated to fill the gap. Full accounting: fiverr-project-archive.

"Delivered a clean, efficient solution ahead of schedule." — Upwork client · n8n workflow build · Nov 2025

"Labels, filters, and folders were set up perfectly, saving me a lot of time." — Fiverr client, United Kingdom · mailbox organisation · Aug 2026

"The Jotform was built exactly as requested. Clean layout, smooth functionality." — Fiverr client, Germany · client intake form · Aug 2026

"Drive was organized and really helped me and my team out." — Fiverr client, United States · Drive reorganisation · 2025

"Great to work with. Have done several projects." — repeat Fiverr client, United States · Sep 2026

• Upwork — upwork.com/freelancers/skmalik1
• Fiverr — fiverr.com/skmalik166

Open to short migrations and cleanups, workflow builds, integration work and ongoing automation support.