Connect Namely

Namely is an HRIS integration that syncs employee, job, and compensation data to Pave using an API key.

Before you connect

• You need access to the API section in Namely. If you don't see this option, contact your Namely administrator.
• You need to be able to generate a Personal Access Token in Namely.
• You need your Namely company ID. This is the subdomain in your Namely URL (for example, if your URL is acme.namely.com, your company ID is acme).

Connect Namely to Pave

1. Log in to Namely.
2. Select API.
3. Select Personal Access Tokens.
4. Select Generate a Personal Access Token. Copy the token.
5. In Pave, go to Connections and find Namely.
6. Enter your API token (the Personal Access Token you just generated).
7. Enter your Company ID (the subdomain from your Namely URL, not the full URL).
8. Click Submit. Pave runs a verification sync to confirm the connection is working.
9. Go to Connections and verify the Namely integration shows as In sync.

Troubleshooting

Connection fails on submit Check that you entered your company ID as just the subdomain (for example, acme), not the full URL (acme.namely.com). Also confirm your Personal Access Token is correct and has not expired.

No data appears after connecting Namely may take a few minutes to return data after the connection is established. If data still does not appear, try disconnecting and reconnecting the integration.

Data is missing or incomplete Pave excludes inactive employees and service accounts from the sync. If specific employees are missing, check their status in Namely. If location data is missing, Pave falls back to the employee's mailing address when no office location is set.

Fields that sync

Custom mappings may apply to your account.

• First name, last name, preferred name
• Work email
• Date of birth
• Job title, department, level, job code
• Employment type
• Manager
• Start date, departure date
• Work location (city, state, country, zip, address)
• Base pay, currency
• Target commission
• Signing bonus, relocation bonus

Additional data

• Compensation history: Not supported. Pave syncs current compensation only.
• Custom fields: Supported. Contact your Pave team to configure custom field mappings.
• Benefits: Not supported.