BambooHR and SyncSignature
BambooHR handles your employee data. SyncSignature handles the email signatures. When BambooHR updates a record in Google Workspace or Microsoft 365, SyncSignature picks it up and updates the signature. No extra connector. No manual work.
5-seat minimum. Annual billing. No card required for trial.
How BambooHR and SyncSignature work together
SyncSignature does not connect to BambooHR directly. The integration works through the directory layer. BambooHR provisions employees into Google Workspace or Microsoft 365 using its native HRIS sync, configured at Account > App Integrations > Google Workspace, or via Azure AD (Entra ID) User Provisioning for Microsoft 365 customers.
SyncSignature connects to Google Workspace via the Admin SDK and Gmail API, or to Microsoft 365 via Microsoft Graph API and an Outlook add-in deployed through Microsoft 365 Centralized Deployment. Once those connections are in place, any employee update BambooHR writes into the directory, including new hires, title changes, department moves, and terminations, shows up in SyncSignature within the next sync cycle. SyncSignature reads the updated directory record and rewrites the signature. No one needs to touch SyncSignature. No one needs to touch BambooHR. The pipeline runs itself.
Offboarding in BambooHR removes the signature automatically
In most signature tools, deprovisioning a departing employee is a manual step. IT marks the employee as terminated in the HRIS, suspends the Google Workspace or Microsoft 365 account, and then opens the signature tool to remove the user from the roster. Three steps, three systems, three places it can be missed.
SyncSignature removes that manual step. When a BambooHR admin marks an employee as terminated, BambooHR's Google Workspace integration suspends the Google account on the next sync cycle, default 6 hours, configurable on the Advantage plan. SyncSignature reads directly from the Google Workspace directory and detects the suspended status on its next run. The signature assignment is removed automatically. No admin touches SyncSignature. The full chain from BambooHR termination to signature removal runs under a day in most configurations.
For companies with regular employee turnover, this matters. A departing rep's signature on their last day still advertises them as an active employee. Without automation, that signature sits there until someone remembers to clean it up. The BambooHR to SyncSignature pipeline never forgets.
How it works
Three systems, one automatic pipeline. You do not configure anything in SyncSignature when an employee record changes in BambooHR.
Employees live in BambooHR
Your HR team manages headcount, roles, titles, departments, and custom fields in BambooHR. BambooHR is the authoritative source for people data.
BambooHR provisions to Google Workspace or Microsoft 365
For Google Workspace, BambooHR syncs through its native Google Workspace app integration (Account > App Integrations > Google Workspace). Default sync cadence is every 6 hours, configurable on the Advantage plan. For Microsoft 365, BambooHR connects through Entra ID (Azure AD) User Provisioning in the Entra admin center. Azure AD typically runs provisioning every 40 minutes.
Connect SyncSignature to your email platform once
In SyncSignature, authenticate with your Google Workspace super-admin account, or connect your Microsoft 365 tenant through the Microsoft Graph API consent flow and deploy the Outlook add-in via Microsoft 365 Centralized Deployment. SyncSignature reads the directory, pulls every user record, and assigns the correct signature template based on group, role, or department rules you configure.
Signatures stay current automatically
Every subsequent change BambooHR writes into the directory, including new hires, role updates, and terminations, triggers a SyncSignature sync. The signature updates. Terminated employees lose their signature assignment. No one needs to open SyncSignature for routine changes.
What this covers
Any employee data BambooHR syncs into Google Workspace or Microsoft 365 can feed into SyncSignature signature templates. Name, title, department, location, phone number, manager, and any custom field mapped into the directory profile is available for signature variables. Role or department changes in BambooHR that propagate into the directory reflect in the signature within the next sync cycle, not days. New hire signatures are ready on day one, assuming BambooHR's sync has run since the new hire record was created. Departing employees lose their signature assignment as soon as BambooHR's deprovisioning reaches Google Workspace or Microsoft 365.
Group-based signature targeting uses the department, cost center, or custom group fields BambooHR writes into the directory. Marketing sees one signature template. Sales sees another. Engineering sees a third. All assignments happen automatically based on what BambooHR writes into the directory profile.
What SyncSignature does not do with BambooHR
SyncSignature does not read from the BambooHR API directly. If an employee update exists only in BambooHR and has not yet synced to Google Workspace or Microsoft 365, SyncSignature does not see it. The pipeline depends on BambooHR's native directory sync being active and healthy.
BambooHR custom fields require the Advantage plan with API access. If you are on BambooHR Essentials, custom field mapping is not available, which limits what signature variables you can pull from BambooHR.
SyncSignature does not interact with BambooHR's own Employee Community signature feature, which is a lightweight internal BambooHR messaging signature separate from Gmail or Outlook email signatures. The two systems do not overlap.
SCIM provisioning directly into SyncSignature is not available. SSO login to the SyncSignature admin panel is not supported. On-premise Exchange is not supported.
BambooHR native vs BambooHR with SyncSignature
| Capability | BambooHR alone | BambooHR + SyncSignature |
|---|---|---|
| Employee data in Gmail/Outlook signature | Requires manual per-user setup | Automatic from BambooHR sync |
| Title/department updates reach signatures | Manual update by each employee | Automatic on next sync cycle |
| New hire signatures on day one | Employee sets their own | Deployed before first email send |
| Offboarding removes signature | Manual cleanup by IT | Automatic when BambooHR deprovisions |
| Group-based signature targeting | Available via directory groups | |
| Signature link click analytics | ||
| Marketing-controlled template | Admin-managed centrally | |
| Banner campaigns (promotions, events) |
Pricing
SyncSignature Teams starts at $2 per user per month, billed annually. Minimum 5 users. Includes directory sync, signature templates, group targeting, banner campaigns, click analytics, and multi-workspace support. 7-day free trial, no card required.
Annual billing only. Pricing scales down from $2 to $1.40 per user at 100 users. The Solo plan at $6 per month covers individual users. The Agency plan covers unlimited clients with per-client workspaces and scoped admin roles.
BambooHR and SyncSignature: common questions
No. SyncSignature does not have a native BambooHR connector. The integration runs through the directory. BambooHR provisions employees into Google Workspace or Microsoft 365. SyncSignature reads from the directory and updates signatures from there.
No setup in BambooHR is needed beyond making sure your HRIS to directory sync is active. If BambooHR is already syncing to Google Workspace via the app integration, or to Microsoft 365 via Entra ID User Provisioning, SyncSignature works with whatever is in the directory.
The default BambooHR to Google Workspace sync cycle is 6 hours, configurable on the Advantage plan. Azure AD provisioning from BambooHR typically runs every 40 minutes. SyncSignature runs its own sync on top of that, typically within a few minutes of the directory update landing. Total propagation from a BambooHR update to a visible signature change is usually same-day. For faster propagation, trigger a manual sync in SyncSignature after a batch change in BambooHR.
Yes, if the custom field is mapped into a Google Workspace directory profile field through BambooHR's API integration. Custom field mapping requires the BambooHR Advantage plan. Once the field lands in the directory profile, SyncSignature reads it and makes it available as a signature template variable.
BambooHR's default Google Workspace sync does not map the preferred name field. If your company uses preferred names, this needs to be mapped manually in BambooHR's Google Workspace integration settings or via the API integration. Once mapped, the preferred name is available in SyncSignature signature templates.
When BambooHR's sync reaches Google Workspace or Microsoft 365, the terminated employee's account is suspended. SyncSignature detects the suspended status on its next sync and removes the signature assignment. No manual cleanup.
No. SyncSignature only consumes directory profile fields from Google Workspace or Microsoft 365. Time tracking and payroll data are not part of the directory sync and are not available to signatures.
Yes. SyncSignature maps signature templates to user groups, departments, or roles as they appear in the directory. If BambooHR writes department and job title fields into the directory profile, those fields are available for group-based targeting rules inside SyncSignature.
Google Workspace (Gmail on desktop, web, and mobile, plus third-party clients connected via Gmail) and Microsoft 365 (Outlook on desktop, Mac, web, and mobile via an Outlook add-in deployed through Microsoft 365 Centralized Deployment). On-premise Exchange is not supported.
SyncSignature Teams starts at $2 per user per month, billed annually. Minimum 5 users. Pricing scales down to $1.40 per user at 100 users. 7-day free trial, no card required.
Connect BambooHR to your email signatures in under 30 minutes
Authenticate Google Workspace or Microsoft 365 once. BambooHR's sync does the rest.
5-seat minimum on Teams. Annual billing. No card required for trial.