> ## Documentation Index
> Fetch the complete documentation index at: https://help-empuls.xoxoday.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PeopleStrong

> Learn how the PeopleStrong and Empuls Integration works and helps automate Employee Engagement, Recognition & Rewards

Empuls and PeopleStrong help you automate user data management for large-scale employee management.

<Warning>
  **Supported organization size:** This integration is designed for organizations with up to **1,000 employees**. The API-based sync processes a maximum of 1,000 employee records or updates per day. If your organization has more than 1,000 employees — or expects more than 1,000 updates in a day — contact your Xoxoday account manager about the **SFTP** option for high-volume syncs.
</Warning>

## Before You Begin

You'll need admin access to both PeopleStrong and Empuls. Obtain your PeopleStrong API credentials and, if needed, SFTP access details.

**With this integration, you can:**

* You can automatically sync data to Empuls when you add new hires, delete exited employees, and update employee data in PeopleStrong.
* Import employee birthday and work anniversary data from PeopleStrong to celebrate these special days with automated greetings and gifts.

Once this integration is enabled, the data syncs once every 24 hours between Empuls and your PeopleStrong account.

**Data can be mapped for**

1. First name
2. Last name
3. Official email
4. Employee code/ID
5. Grade
6. Department
7. Designation
8. Date of birth
9. Date of Joining
10. Mobile number
11. Business Unit
12. Cost center
13. Location
14. Contact/Mobile number, and many more

### **Ways to connect PeopleStrong with Empuls**

You can choose one of the following options based on how your PeopleStrong instance is set up

###

\*\*Option A: Legacy mesh-web-api \*\*

Configure from the Empuls front end. You’ll need:

* **Realm ID**
* **Integration Name**
* **API Key**
* **Authorization Key**

Best for: Existing (legacy) PeopleStrong tenants already using mesh-web-api.

### Option B: cURL/Postman-based setup (for newer clients)

We configure from the backend. Share either your Postman collection or cURL endpoints.

Provide two endpoints:

1. Token endpoint (to fetch the auth token)
2. Employee Data endpoint (to fetch employee master data)

You can share these with your Xoxoday account manager, and our technical team will complete the configuration.

After configuration: please contact the PeopleStrong team to reset the data so Empuls can fetch fresh records from the start.

​Caveat (API throughput): This API-based approach can fetch up to 1,000 employee records/updates per day.
​
If your total employee count or daily updates exceed 1,000, we recommend using SFTP for the integration.

### SFTP (recommended for large volumes)

For organizations with large headcounts or frequent updates, SFTP ensures reliable, high-volume, and scheduled data loads without daily API limits. Your account manager can help you evaluate and enable the SFTP route.
​
Sync cadence

* **Frequency:** Once every 24 hours
* **Direction:** PeopleStrong → Empuls (source of truth remains PeopleStrong)

**How to get started**

<Steps>
  <Step title="Decide your method">
    Choose Option A (mesh-web-api) or Option B (cURL/Postman).
  </Step>

  <Step title="Share required details">
    * **Option A:** Realm ID, Integration Name, API Key, Authorization Key (configure in Empuls UI).
    * **Option B:** Token & Employee Data endpoints (Postman collection or cURL) to your Xoxoday account manager.
  </Step>

  <Step title="Xoxoday config">
    Our experts will complete the setup (front end for A, back end for B).
  </Step>

  <Step title="PeopleStrong reset">
    Ask the PeopleStrong team to reset data so Empuls receives fresh records.
  </Step>

  <Step title="Validate">
    We’ll run a test sync and confirm user counts and sample records.
  </Step>

  <Step title="Go live">
    Automated daily sync starts.

    <Note>Questions? Contact us at [cs@xoxoday.com](mailto:cs@xoxoday.com).</Note>

    ##
  </Step>
</Steps>