Connector to Namely

With the Namely® connector, you can use commands in a chain to interact with Namely. For example, with this connector, you can:

• Find user profiles in Namely
• Download reports created in Namely

Note: This connector is built by Workiva and connects to a third-party system. While our Support team can help configure this connector within your workspace, we are unable to troubleshoot or otherwise assist with any issues that originate outside of the Workiva platform.

Prerequisites

To enable the connection, the connector use the Namely REST API. To set up the connector, you'll need:

• An API personal access token created in Namely for the connector
• Your organization's Namely subdomain

Note: In the URL for your organization's Namely instance, the subdomain appears before .namely.com.

Create a Namely personal access token

To secure the connection to the Namely API, the connector requires a bearer token—known as a personal access token (PAT)—created in Namely.

1. In Namely, select API.
   
2. On the Personal Access Tokens tab, enter a unique name to identify the connector's token, and click Create.
   
3. Copy the PAT that appears for the connector's configuration.

Set up the Namely connector

Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.

1. From Chain Builder, click Connections  compare_arrows, and then Create at the top right.
2. Under BizApp Connection, select Namely and the default CloudRunner.
   
3. Under Basic Info, enter a unique name and description to help identify the connection.
4. Under Properties, enter the connector's details:
   
   

   Property	Details
   Personal access token	Enter the API bearer token created in Namely for the connector.
   Subdomain	Enter the subdomain for your organization's Namely. In the Namely URL, your subdomain appears before .namely.com.

5. Select the environments to use with the connection, and click Save.
6. To test the connection, create and run a chain with the connector's Get Report command, and verify it returns a valid output.

Troubleshooting

If the connection to Namely fails:

• Verify the connector's Namely PAT. If necessary, create and configure a new token for the connector.
• Check your organization's Namely subdomain. In the Namely URL, your subdomain appears before .namely.com.