Skip to main content

Namely setup

Namely connects through the unified HRIS connector. This page covers the Namely-side configuration you complete first. Once it's done, add the connector in Mesh by following Connect your HR system.

You finish with two values:

ValueWhere it comes from
SubdomainThe first label of your Namely URL
Personal access tokenAdmin → API

Before you start

You need administrator access to your company's Namely instance.

Third-party product

These steps reflect Axiad's current understanding of Namely's configuration. Because Namely is a third-party product, there may be variations between your experience and what this guide describes, depending on the version in use and recent updates.

If you find a significant difference, or anything that doesn't make sense, let us know through Axiad support.

Step 1 — Find your subdomain

Your subdomain is the first label of the URL you sign in at. If you sign in at acme.namely.com, the subdomain is acme.

The connection window asking for the Namely subdomain

The subdomain entered in the connection window

Step 2 — Create a personal access token

  1. Under the Admin dropdown, select API.

    The Namely admin menu with the API item

  2. Open the Personal Access Tokens tab at the top left.

  3. Name the token — something identifying the Axiad Mesh connection — and select Create.

  4. Copy the token.

    The created personal access token

Step 3 — Connect in Mesh

Follow Connect your HR system, choose Namely in the connection window, and supply the subdomain and token.

After connecting

The connector appears in your connectors list with Health: Initializing while the first collection runs, then moves to Good. Access is read-only: Mesh does not write back to Namely.

If it doesn't come online, see Troubleshoot HR connectors.

Troubleshooting

What you seeLikely causeFix
Authentication failsThe full host was entered instead of the subdomainEnter only the first label, for example acme
The token was created on the wrong tabOAuth applications and personal access tokens are differentUse the Personal Access Tokens tab