Submit a ticket
Welcome
Login

Mapping Teamtailor custom fields to Oneflow data fields

You can now map Teamtailor custom fields to Oneflow data fields. This article covers three parts that make up the custom field managing process: 


TABLE OF CONTENTS


Part 1. Setting up Teamtailor custom fields


Note: The Oneflow admin email address is required to map Teamtailor custom fields to Oneflow data fields. You can configure the admin email address on the Teamtailor settings page. If the admin field is empty, Teamtailor will use the recruiter for which you opened the configuration. However, this is only required if there are some pending custom fields to map.

The setup process consists of the following steps: 

  1.  In the Teamtailor administrator account, go to Settings → Custom fields.
  2. Create a new or choose an existing custom data field that you want to access in Oneflow contracts. 
  3. In the API name field, add the"oneflow-" prefix to the custom field, as shown below:
  4. Click Save to save your custom data field. 

That's it!  You can now use this custom data field value in your Oneflow contracts. 

Note: Make sure the custom field value is updated in Teamtailor to match the given data field in Oneflow.


Part 2. Using custom data fields in Oneflow

Now that you have the custom data field set up in Teamtailor, it's available in your Oneflow contracts and templates. 

To use your custom data field:

  1. In Oneflow, open a contract and edit an existing form field or add a new one.
  2. Click the Edit icon, and in the Edit field menu > Data field, select your custom field. 
  3. The custom data field value will be prepopulated in the selected form.

Part 3. Deleting custom fields 

To remove a custom field, remove the "oneflow-" prefix in the custom field settings. Next time you open the integration configuration, Teamtailor will request to remove these data fields. 


Note: If a user deletes a custom field in Teamtailor, it will also be removed from Oneflow. However, the deleted data fields will still be visible until the user creates the next contract.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.