Google Meet Networking Add-on
A Google Meet add-on built for a Toronto-based networking company that allowed users to create networking events directly inside live meetings. The add-on integrated with Google Workspace APIs and the client’s backend systems to streamline virtual event coordination without requiring participants to leave the meeting.
The problem
After successfully delivering a Slack integration, the client wanted a similar workflow available inside Google Meet. Their users frequently coordinated networking events during live calls, but event creation still required switching to the company website. The goal was to create a lightweight in-meeting workflow that allowed users to submit event details, generate event links, and receive confirmation data directly from a Google Meet side panel.
Key decisions
Building around a newly released platform ecosystem
The add-on was developed during the early stages of the Google Meet add-ons ecosystem, where documentation and examples were still limited. Many expected behaviors were undocumented or inconsistent, requiring extensive experimentation with Google Workspace APIs, SDK behavior, authentication flows, and deployment tooling. Much of the engineering process involved piecing together functionality from fragmented examples, debugging platform limitations, and validating assumptions through trial and error.
Embedded meeting workflow design
The add-on launched directly inside a live Google Meet session through a side-panel interface built using Node.js and HTML/CSS. Users could enter event information without leaving the meeting, allowing networking workflows to happen naturally during calls. The interface was intentionally designed to be minimal, responsive, and aligned with the client’s branding so that the experience felt integrated into the meeting environment rather than external to it.
Real-time backend communication and response handling
The add-on securely communicated with the client’s backend infrastructure to create events and retrieve generated identifiers, links, and confirmation data in real time. Because the integration relied on external systems outside the add-on itself, significant effort went into handling network failures, backend downtime, invalid responses, and incomplete submissions gracefully while still maintaining a smooth user experience.
Google Cloud and Workspace integration
The project required configuring and integrating multiple Google services, including Google Cloud tooling, Workspace APIs, authentication flows, and add-on deployment configuration. Since official examples primarily focused on JavaScript-based implementations, the project was developed in Node.js to align closely with the available platform guidance and SDK behavior.
Extending an existing business workflow into collaboration software
Rather than rebuilding the company’s event system from scratch, the add-on extended the client’s existing backend workflows into Google Meet. This allowed the company to preserve their existing infrastructure while making event creation accessible directly from the communication tools their users already relied on daily.
Outcome
The add-on was successfully delivered as a continuation of the client’s platform integration strategy following the Slack project. It reduced friction during virtual networking sessions by allowing participants to create and share event information directly inside meetings. The project also provided valuable experience working with immature SDK ecosystems, sparse documentation, and rapidly evolving platform tooling.
What I learned
This project taught me how to work effectively in environments where official documentation alone is not enough. Building on top of a relatively new platform required patience, experimentation, and a strong understanding of underlying web and API fundamentals. It also strengthened my experience with Google Workspace integrations, cloud tooling, and designing embedded workflows inside collaboration platforms.