Skip to main content

Documentation Index

Fetch the complete documentation index at: https://empuls.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The Freshteam integration keeps Empuls in sync with your Freshteam HR system. Once connected, Empuls reads your employee records from Freshteam — names, emails, departments, designations, employment status — so you don’t have to maintain the same list in two places. New hires, role changes, and exits flow into Empuls without manual CSV uploads. Open the integrations hub in your tenant at https://<your-empuls-url>/home/integrations and click Freshteam.

​
Before you start

  • You must be a Super Admin in Empuls.
  • You need an admin account in Freshteam with permission to authorize third-party apps.
  • Decide which Freshteam users should be active in Empuls (the integration respects Freshteam’s active/inactive status).

​
How the integration works

1

Open the Freshteam card

From the Integrations hub, locate Freshteam and click Configure.
2

Authorize Empuls in Freshteam

Empuls redirects you to Freshteam’s OAuth consent screen. Sign in with a Freshteam admin account and approve the requested scopes.
3

Confirm the directory preview

After authorization, Empuls fetches a preview of your Freshteam directory so you can verify the right tenant is connected.
4

Map fields

Default field mapping covers first name, last name, email, designation, and employment status. Adjust the mapping if your Freshteam tenant uses custom fields.
5

Run initial sync

Click Start sync. Empuls imports active Freshteam users as Empuls employees. Subsequent changes sync automatically on a recurring schedule.

​
What syncs

Freshteam fieldEmpuls field
First nameFirst Name
Last nameLast Name
Work emailEmail (primary identifier)
Designation / TitleDesignation
DepartmentDepartment
Reporting managerReporting manager
Employment statusActive / Inactive
When an employee is marked inactive in Freshteam, Empuls applies your employee exit policy to handle points, custom budgets, and pending nominations.

​
Sync history

The sync history page shows each run with timestamp, records added, records updated, and records failed. Click any row to see per-record details and error reasons (for example, “duplicate email”, “missing required field”).

​
Reconnect or disconnect

  • Reconnect — Re-run the OAuth flow if scopes need to be refreshed (Freshteam admin policy change, expired token).
  • Disconnect — Stop the recurring sync. Existing Empuls users are not removed; you’ll need to manage them in Empuls directly going forward.

​
Limits and gotchas

  • Freshteam is the source of truth for the synced fields. Edits in Empuls to a synced field are overwritten on the next sync.
  • Custom Freshteam fields require a manual mapping step the first time they appear.
  • The integration uses Freshteam’s standard rate limits. Very large directories may take multiple sync cycles to fully reflect.