Stop wrestling with Google's Admin SDK and Directory API. Bindbee gives you a single unified API to sync employee profiles, organizational data, payroll, benefits, and more from Google Workspace—alongside 60+ other HR systems—without the maintenance headaches.
Bindbee normalizes Factorial's data into unifiedBindbee normalizes Google Workspace's directory and organizational data into unified models. One integration, consistent data structure across every HR system your customers use. models. One integration, consistent data structure across 60+ HR systems.
Your end-user authenticates their Google Workspace admin account through Magic Link—our drop-in auth component. They authorize via OAuth, and the connection is live in minutes.
We pull user profiles, organizational data, and more from Google Workspace's Directory API and normalize everything to Bindbee's unified models. Initial sync completes in minutes, then automatic incremental syncs keep data fresh.
One REST API to get normalized employee, employment, payroll, and benefits data. The same endpoint structure works for Google Workspace and 60+ other HR systems.
Customers authenticate effortlessly via Magic Link, with an embeddable SDK that enables seamless, in-app connections.
Most customers complete setup in under 10 minutes. Your end-user authenticates their Google Workspace admin account via Magic Link using OAuth, and the initial data sync begins immediately.
Your customer needs admin access to their Google Workspace account. Magic Link handles the OAuth flow—they simply authorize the connection. No API keys or service account credentials need to be shared.
Yes. Enable include_custom_fields=true in your API requests to receive any custom user attributes configured in Google Workspace's directory schema. Custom fields appear in the custom_fields object with their original field names.
After the initial sync, Bindbee runs automatic incremental syncs. Frequency depends on your plan. You can also trigger manual syncs via the API or dashboard anytime you need the freshest data.
Yes. The manager field on Employee objects contains the manager's Bindbee ID. You can expand this to get full manager details. Department, division, and organizational unit data is also available through the Employment model.
Yes. Use employment_status=INACTIVE or check the termination_date field. Historical user data remains accessible through the API even after an account is suspended or deleted in Google Workspace.
You don't. Bindbee manages rate limiting with Google's Admin SDK internally. We cache synced data and handle retries automatically. Your requests to Bindbee's API are subject to your plan's rate limits.
Yes. Bindbee is SOC 2 Type II certified, HIPAA compliant, and GDPR ready. Data is encrypted in transit (TLS 1.2+) and at rest. We never store your customer's Google Workspace credentials—authentication uses OAuth tokens managed securely.
Yes. Configure webhooks to receive notifications when connector syncs complete, employee data changes, or sync errors occur. See our webhooks documentation for setup details.
Absolutely—that's the whole point. Bindbee normalizes Google Workspace user data into the same unified models used for BambooHR, Workday, ADP, and 60+ other systems. Your code works the same regardless of which HR system your customer uses.
