Slack Event Automation Platform
A custom Slack application built for a Toronto-based networking company focused on connecting students, job seekers, mentors, and employers. The platform allowed organizers and participants to create, join, and manage networking events directly inside Slack without needing to visit the company website.
The problem
The client’s event registration and onboarding workflow existed entirely on their website, creating unnecessary friction for users already communicating inside Slack. The goal was to build a native Slack experience that mirrored the company’s existing event system while integrating directly with their backend infrastructure. The application needed to support event creation, participant onboarding, automated channel management, authentication, and marketplace-level reliability.
Key decisions
Interactive Slack workflows built around roles and permissions
The application used Slack Block Kit components, interactive buttons, and modal-based workflows to create a structured onboarding experience. When the app was added to a workspace, it posted an interactive message containing separate actions for organizers and participants. Event creation functionality was restricted to administrators, while registration workflows were accessible to all users. This required carefully handling Slack permissions, event subscriptions, user validation, and interaction payloads while keeping the experience intuitive for non-technical users.
Automated event channel creation and onboarding flows
When an administrator created an event through the modal interface, the application automatically generated a dedicated Slack channel for the event, synchronized the submitted data with the client backend, and distributed event information back into Slack. Participants could then complete their own onboarding flow through a separate modal interface, after which the application automatically added them to the event channel and posted their introduction message. The result was a fully integrated workflow that removed the need for users to manually coordinate event participation outside the platform.
Backend integration and API synchronization
The Slack application did not own the underlying business logic. Instead, it acted as an integration layer communicating with the client’s existing backend APIs using the same workflows their website relied on. Submitted event and participant data were forwarded to the backend, processed externally, and returned with generated identifiers, event metadata, and links. The application then translated those responses into user-facing Slack workflows. Designing around an external API contract required careful handling of asynchronous responses, validation errors, and backend downtime scenarios.
OAuth 2.0 authentication and secure credential handling
The integration implemented full OAuth 2.0 flows for Slack workspace installation and authorization. Tokens and credentials were securely stored and managed using PostgreSQL-backed session handling and encrypted storage practices. Because the application was designed with marketplace publishing standards in mind, special attention was given to permission scopes, security practices, and user transparency around data access.
Designing a polished user experience inside Slack
A major focus of the project was making the integration feel natural inside Slack rather than behaving like a thin wrapper around a website form. Considerable effort went into designing polished modal layouts, structured form flows, contextual direct messages, and clear status feedback. The application proactively informed users when actions succeeded, failed, or required additional attention, significantly improving usability and reducing confusion during onboarding.
Outcome
The application was successfully delivered and deployed for the client as part of their networking platform infrastructure. It streamlined event creation and participant onboarding while reducing the need for users to leave Slack to interact with the company’s services. The project remains one of my favorite engineering experiences because it was built during the period where I was first learning APIs and third-party platform development, yet still evolved into a polished production-quality system.
What I learned
Building this project taught me how to work deeply with event-driven APIs, third-party SDKs, authentication flows, and production integration constraints. It also reinforced the importance of thoughtful UX design in backend-heavy systems. Working through Slack’s documentation and marketplace requirements forced me to think carefully about permissions, reliability, edge cases, and user communication in a real-world environment.