Skip to main content

Wemply

Learn how candidate information from Teamdash is shared with Wemply

Rando Aljaste avatar
Written by Rando Aljaste
Updated over a week ago

The Wemply–Teamdash integration allows you to seamlessly transfer candidate information from Teamdash to Wemply once a candidate is marked as Hired.

How does this work?

  • Candidate details collected in Teamdash are automatically sent to Wemply.

  • A new profile is created in Wemply with the transferred information, so your HR team can immediately continue the onboarding process.

  • This eliminates manual data entry and reduces the risk of errors.

Integration set up

  • Open Teamdash and go to the Settings

  • Navigate to the API menu, which is under the Administration section, and click on the '+ Create key' button

  • Add the Key name (e.g., "Wemply"). This will be internally visible in Teamdash.

  • Give permission to Read candidates and untick everything else.

  • Save the new API Key.

  • Click to reveal the value and copy the key.

  • Next up, go to Wemply and open the Integrations there

  • Add a new integration with Teamdash

  • Add a subdomain. If your Teamdash domain is yourorganizationname.teamdash.com, then the subdomain is yourorganizationname.

  • Add the API Key that you previously copied

  • Assign the new user permission group to be 'Tavakasutaja'

  • Save the integration

If you are having issues with adding the integration in Wemply, please contact their support.

How to send candidate information to Wemply?

You can send candidate information to Wemply by moving the candidate to a stage that has the Hired category assigned to it. Information is sent to Wemply automatically every full hour.

Teamdash will forward the following candidate profile fields to Wemply:

  • First name

  • Last name

  • E-mail address

  • Phone number

  • Country

Additional details can be filled in by the new employee through Wemply's self-service tool.

For further questions, please contact the Teamdash Support team via [email protected].

Did this answer your question?