|

Overview

I designed and built a Slack-based reclamation management system that turns Slack into an internal operations interface for handling reclamation cases across multiple regions.

The system combines Slack App Home, Slack modals, n8n, Microsoft Graph, and Excel into one workflow-driven case management tool.

Instead of manually opening Excel files for every action, users can create new reclamation cases, search existing cases, update records, generate reports, and receive confirmation messages directly inside Slack.

The workflow uses Slack App Home as the user interface, n8n as the automation backend, and Excel as the operational data layer.

The challenge

Reclamation cases had to be tracked across multiple operational locations, with different statuses, priorities, responsible people, customer details, financial values, risk levels, and follow-up notes.

The challenge was to create a simple internal interface that allowed the team to manage reclamations directly from Slack without manually navigating region-specific Excel sheets for every action.

The system needed to support creating new cases, searching existing cases, updating case information, generating region-based reports, and giving users immediate feedback after their actions.

What I did

I designed, built, tested, and maintained the automation layer that turns Slack into an internal reclamation management interface.

My work covered the full automation layer: building the Slack App Home dashboard, handling button clicks and modal submissions, and reading and writing Excel data through Microsoft Graph. I also implemented the region-based report generation, user validation, and the confirmation message flow that gives users feedback after each action.

System flow

Core modules

Technical decisions

Reliability patterns

The outcome

The automation made the reclamation process more structured and easier to manage directly from Slack.

It reduced the need to manually navigate Excel files for everyday actions and gave the team a central place to create, search, update, and report reclamation cases.

The most important impact was operational visibility: users could see reclamation status across regions, create structured records, search existing cases, generate reports, and receive immediate confirmation after actions.

Tech stack

Proof / Evidence

This case study is based on a Slack-based internal case management workflow. The architecture is documented openly. The raw workflow export is not published, since it contains customer data, Slack workspace identifiers, and internal workbook references.

Live system

Click to enlarge

Public code & documentation

Code excerpt: Slack payload parser with allow-list

The first node of the interaction-handling workflow. Parses the URL-encoded Slack interaction payload, then checks the requesting user against a hard-coded allow-list before any downstream branch executes. This is appropriate for a closed team and documented as the right shape to replace for broader use.

// First node of the interaction-handling workflow.
// Parses the URL-encoded Slack interaction payload, then
// checks the requesting user against an allow-list before
// any downstream branch runs.

const body = $input.first().json.body;

const ALLOWED_USERS = [
  "U_AAAAAAAAAA",
  "U_BBBBBBBBBB",
  "U_CCCCCCCCCC",
];

const requestUserId = (() => {
  try {
    const p = typeof body.payload === "string"
      ? JSON.parse(body.payload)
      : body.payload || {};
    return p.user?.id || "";
  } catch (e) {
    return "";
  }
})();

if (!ALLOWED_USERS.includes(requestUserId)) {
  return [{ json: { blocked: true, userId: requestUserId } }];
}

// ... continues with action / region / view-state extraction.
// See snippets/slack-payload-parser.js for the full parser.

Full version, with action and region extraction, in snippets/slack-payload-parser.js. Four other snippets in the same repository cover Block Kit modal building, Slack thread context extraction, LLM agent prompt construction, and date-range summary aggregation.