Namely

Namely provides a comprehensive HR platform that centralizes employee data and streamlines HR processes. They help manage payroll, benefits, and talent development efficiently.

To integrate Namely to Relyance AI, you will need a Personal Access Token (PAT).

In Namely

1. Log in to your Namely account as an Admin.
2. Click on your profile icon in the top toolbar, then select API from the dropdown.
3. Find and select the Personal Access Tokens tab.
4. Provide a meaningful name for your token (e.g., Relyance AI Scan) and click Create.
5. Copy the newly generated token and store it in a safe location. It will not be displayed again. This token will be used as the API Token in the following steps.

Please make sure to review and adopt the best practices for creating and maintaining Personal Access Tokens in the following Namely article: Authentication - Personal Access Tokens (PATs)

In the Relyance AI application

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the Namely integration card and click on it.
5. Click on the Add Connection button on the top right.
6. Provide a meaningful name for the integration and click on the Add button.
7. In the Overview section, review the Scope and Permission, and Endpoint details and click on Continue. For more details on the additional configuration, see Integration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, provide the following information and click on Authenticate.
   • URL (your Namely instance URL, for example https://boutique.namely.com)
   • API Token (Personal Access Token saved from In Namely section above)
10. Review the configuration summary from the Completion section and click on Finish.

11. Confirm the integration Status reflects Connected.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A credential rotated at the vendor is not picked up here. API Token is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. Check the address fields before suspecting the credentials. Url identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "namely" {
  vendor = "namely"
  name   = "<your connection name>"

  auth = {
    method = "access-token"
    params = {
      url = "https://company.namely.com"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      token = var.namely_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}