Employee directory with Slack integration and name analytics
Build an internal employee directory that syncs from Slack. The goal is to give HR and employees a single place to see who's on the team, find new hires, and browse public Slack profile info without hitting the Slack API on every page view. Trigger it on a daily schedule to refresh the cache, and serve the directory as a web page. Main steps, at a high level: Pull every internal user's Slack profile (name, profile picture URL, LinkedIn if present) once per day. Cache the result in a dated JSON file (one per day) in durable storage, so the page reads from cache instead of calling Slack on every load. Render a directory page showing profile pictures, names, and tenure, highlighting the newest joiners. Compute simple analytics over the cached data, like the most common first names across the company. Tools used: Slack, 3B named volume (daily JSON cache)
What this prompt builds
An internal team directory that pulls employee data from Slack to display profile pictures, LinkedIn profiles, and tenure information. It shows the newest team members and analyzes the most common first names across the company. Data is cached daily to minimize API calls.
The problem
HR teams and employees need a centralized place to discover new team members, quickly access their LinkedIn profiles, and see company demographics like the most common first names. Without a dedicated directory, it's hard to keep track of who's joined recently or find colleagues across a growing organization. This workflow pulls employee data directly from Slack to create an always-updated internal directory that surfaces profile pictures, tenure information, and fun analytics about the team.
Solution and impact
The workflow automatically syncs employee data from Slack once per day and displays it in an accessible internal directory. Teams can instantly see new hires, click through to LinkedIn profiles, and discover interesting patterns like which first names are most common in the company. By caching data daily rather than loading on every visit, it reduces API calls while keeping the directory fresh and responsive.