Google Workspace Admin
Building a custom integration between Google Workspace Admin and Webflow gives you complete control over user provisioning workflows and authentication systems
How to integrate Google Workspace Admin with Webflow
Building a custom integration between Google Workspace Admin and Webflow gives you control over user provisioning workflows and authentication systems. Sync employee directories to your Webflow site, automate team member onboarding when you add users to your domain, or build internal portals that reflect your organizational structure.
Connect these systems through custom code that authenticates with both the Google Workspace Admin SDK Directory API and the Webflow Data API. Your backend service or serverless functions retrieve user data from Google Workspace, transform it to match your Webflow collection schema, and create or update collection items.
Build with Webflow and Google Workspace Admin APIs
Build custom integrations that sync user data between Google Workspace and Webflow, automate team member provisioning, or create employee portals that pull organizational information from your Workspace directory. Your backend service authenticates with both the Google Workspace Admin SDK and Webflow API, retrieves user data from the Directory API, transforms JSON responses to match your Webflow collection schema, and creates or updates collection items.
Set up OAuth 2.0 authentication for both services. For Google Workspace Admin, use service account credentials with domain-wide delegation when you need automated access without user interaction. For Webflow, implement OAuth 2.0 authorization for multi-site integrations or use API tokens for single-site implementations.
This integration enables the following actions:
- Sync user directories with GET /admin/directory/v1/users to retrieve Google Workspace users and store them as CMS items in Webflow collections
- Automate user provisioning by combining POST /admin/directory/v1/users with Webflow's collection items API to create accounts in both systems simultaneously
- Build employee directories using GET /admin/directory/v1/groups to organize team members by department or role in your Webflow site
- Manage organizational units through domain administration endpoints to reflect company structure in your web properties
Your integration server handles authentication tokens, makes API requests to both platforms, and transforms data formats. The Google Workspace Admin SDK returns user objects with properties like primaryEmail, name, and orgUnitPath, which you map to Webflow CMS collection fields.
Consider rate limits when designing your sync logic. Google Workspace Directory API has a limit of 10 user creations per domain per second. Use pagination parameters in the Directory API and implement error handling for both services. The Webflow JavaScript SDK provides TypeScript support and request builders, though full support for v2 APIs is still in development.
Sync employee data to Webflow CMS
Pull user information from Google Workspace and display it on your Webflow site by syncing directory data to CMS collections. This works for employee directories, team pages, or internal dashboards that display current organizational information.
Create a Webflow collection with fields matching your Google Workspace user properties like email, name, department, photo URL, and role. Use GET /admin/directory/v1/users to retrieve users from your domain, then create or update corresponding collection items through POST /collections/{collection_id}/items.
Set up scheduled jobs that run your sync script at regular intervals. Each run compares Google Workspace data with Webflow collection items, creates new entries for added employees, updates existing records when information changes, and optionally archives removed users.
from google.oauth2 import service_account
from googleapiclient.discovery import build
SCOPES = ['https://www.googleapis.com/auth/admin.directory.user']
credentials = service_account.Credentials.from_service_account_file(
'credentials.json', scopes=SCOPES
).with_subject('admin@yourdomain.com')
service = build('admin', 'directory_v1', credentials=credentials)
users = service.users().list(customer='my_customer', maxResults=10).execute()
This Python example from the Google API Python Client samples shows basic Directory API authentication. You'll extend this to fetch all users, then make corresponding Webflow API requests to populate your CMS.
Profile photos require a separate API call to GET /admin/directory/v1/users/{userKey}/photos/thumbnail after retrieving user data.
Implement custom authentication flows
Build authentication systems that verify user identity against your Google Workspace domain before granting access to Webflow content. This pattern works for internal tools, employee portals, or client areas that require Workspace credentials.
Your authentication flow runs on a backend service that validates Google OAuth tokens, checks user permissions through the Directory API, then creates authenticated sessions for your Webflow-hosted application. Use GET /admin/directory/v1/users/{userKey} to verify user details and organizational unit membership after initial OAuth authentication.
This approach requires significant custom backend development. For simpler implementations, consider using third-party tools like Memberstack or Xano that handle Google OAuth integration with less custom code.
Combine this with Webflow's Users API (currently in Beta for the Memberships feature) to manage member access. When a Google Workspace user successfully authenticates, check if they have a corresponding Webflow user account and create one if needed. Store the association between Workspace user IDs and Webflow user IDs in your database.
Implement role-based access control by reading organizational unit data from Google Workspace with the Directory API and mapping it to content access permissions in your Webflow site. For example, users in the "Engineering" organizational unit might access different pages than users in "Sales."
Automate team member onboarding
Connect user creation workflows so that adding someone to Google Workspace automatically provisions their presence on your Webflow sites. This reduces manual work when onboarding employees or contractors who need access to internal web properties.
Monitor Google Workspace for new users through periodic API polling (every 5-15 minutes is typical). When you detect a new user, trigger your integration to create matching records in Webflow. Google Workspace doesn't offer webhooks for user creation events, so polling is required.
Your onboarding automation creates CMS collection items for the new employee, adds them to relevant groups using the Groups API, and optionally sends notifications through Webflow webhooks. Map Google Workspace user properties to Webflow fields where primary email becomes the collection item email field, full name populates the name field, and profile photos sync to image fields.
Handle edge cases like duplicate email addresses, incomplete user profiles, or API failures. Store sync status in your database so you can retry failed operations and maintain an audit log of provisioning actions.
Note that creating users via the Google Workspace API incurs charges on flexible billing plans and counts against license limits.
What you can build
Integrating Google Workspace Admin with Webflow lets you build automated employee directories, authentication systems, and onboarding workflows that stay synchronized with your organizational data.
- Employee directory sites with auto-update: Create searchable team directories that update when you add, modify, or remove users in Google Workspace, displaying current employee information, department assignments, and contact details.
- Automated onboarding pages for new employees: Generate personalized welcome pages and resource hubs that populate when you create their Google Workspace account, including role-specific documentation and team introductions.
- Client portal authentication with Google Workspace credentials: Build secure client areas where Google Workspace credentials control access, allowing your team members to log in with their existing work accounts.
- Organizational structure visualizations: Display company hierarchies, department breakdowns, and reporting structures by pulling organizational unit data from Google Workspace and rendering it as interactive charts in Webflow.
Frequently asked questions
You need specific OAuth 2.0 scopes based on which resources you want to access. Request
https://www.googleapis.com/auth/admin.directory.userfor full user management capabilities,https://www.googleapis.com/auth/admin.directory.groupfor group management,https://www.googleapis.com/auth/admin.directory.domainfor domain administration, andhttps://www.googleapis.com/auth/admin.directory.orgunitfor organizational unit management. The Google Workspace Admin SDK authorization guide explains all three OAuth flows: authorization code flow for web applications, installed application flow for desktop apps, and service account flow for automated systems.For server-to-server integrations that run without user interaction, use service accounts with domain-wide delegation. This lets your integration act on behalf of admin users to read and modify directory data programmatically.
Webflow supports two authentication methods based on your integration scope. Use site tokens for single-site integrations where you're only managing one Webflow project. These tokens work well for internal tools or proof-of-concept implementations.
For production integrations that need to access multiple sites or act on behalf of different users, implement OAuth 2.0 authorization with the authorization code flow. This approach lets users grant your integration access to their Webflow sites without sharing API tokens. Store OAuth access tokens securely and implement refresh token logic to maintain long-running integrations.
The Webflow JavaScript SDK provides built-in OAuth handling and token management, reducing the amount of authentication code you need to write.
Retrieve groups from Google Workspace and store them as CMS items in Webflow. Use GET /admin/directory/v1/groups to list all groups in your domain, then create corresponding collection items through the Webflow CMS API.
Create a Webflow collection with fields for group name, email address, description, and member count. Your integration code retrieves groups from the Directory API, transforms the response data to match your collection schema, and makes POST requests to create or update items. For member relationships, create a separate collection that references both users and groups through reference fields.
Set up webhooks or scheduled jobs to keep group data synchronized. When someone adds or removes group members in Google Workspace, your integration updates the corresponding Webflow collection items to reflect current membership.
The Directory API users resource returns detailed user objects with properties you can map to Webflow CMS fields. Standard properties include
primaryEmail,name(withgivenNameandfamilyName),orgUnitPathfor department or division,thumbnailPhotoUrlfor profile images, andisAdminfor permission levels.Custom schemas let you store additional properties in Google Workspace that your integration can read and sync to Webflow. For example, add custom fields for job titles, office locations, or specializations, then retrieve them through the API and populate corresponding Webflow collection fields.
Design your Webflow collection schema to match the Google Workspace properties you need. Use text fields for names and emails, reference fields for organizational units or departments, image fields for photos, and boolean fields for admin status or other flags.
Implement periodic sync jobs that compare Google Workspace data with your Webflow CMS collections. Use GET /admin/directory/v1/users to retrieve current user information, then check each user against your stored Webflow collection items. When you detect changes, make PATCH requests to update the corresponding collection items.
Track the last modified timestamp for both Google Workspace users and Webflow items to detect changes efficiently. The Directory API doesn't provide webhooks for user changes, so you'll need to implement periodic polling.
Handle deletions by checking which Webflow collection items no longer have corresponding Google Workspace users. You can either delete these items or mark them as archived using a status field in your collection schema.
Description
Google Workspace Admin provides centralized management for your organization's users, groups, domains, and security policies.
This integration page is provided for informational and convenience purposes only.

Google Docs
Google Docs connects to Webflow through direct embedding and third-party applications rather than API integration.

Google Drive
Connect Google Drive with Webflow to embed documents, sync form submissions to spreadsheets, and manage content files directly on your site. For non-API implementations, use Google Drive's embed functionality for Google Docs, Sheets, Slides, and Forms, or use no-code automation platforms.
ClickUp
ClickUp connects to Webflow through third-party automation platforms or direct API integration. Automation platforms like Zapier or Make provide quick setup without code. API integration provides more control for custom workflows.

G Suite
Embed Google Docs, Sheets, Slides & Forms in your site or blog.


