MyNewTerm

Connect Arbor Workflows to MyNewTerm to allow automated kick off of a Onboarding workflow for new starters. This will need to be done before any workflows can be triggered.

How does this work?

For any integration to work, you must authenticate with MyNewTerm. Each individual school needs to provide authentication—you'll then be able to use the integration for any schools that have authenticated.

This trigger can only be used for one workflow. If multiple workflows are set to be trigger by My New Term, they will all be triggered on each transfer of data from My New Term - resulting in duplicate workflow runs.

The trigger form within the MyNewTerm templates has been preconfigured and coded to be triggered by MyNewTerm once it is live and the authentication has happened. Therefore it cannot be edited.

Providing Authentication for MyNewTerm

Setting up authentication with MyNewTerm involves several steps. Since this process cannot be fully automated, follow these instructions:

1. Navigate to the settings page and School settings.
2. Click on integrations, then select the MyNewTerm integration.
3. You'll see a list of your schools. You need to add an API key for each school. The same API key can be used for multiple schools if they share a MyNewTerm instance.

1. Click on "Authenticate" for the school you wish to add an API key for.
2. Select and copy the generated API key.
3. Next, head to MyNewTerm.

 

MyNewTerm

Ask your account manager to enable Arbor Workflows

Request that your MyNewTerm account manager enables the integration on your account.

Log into your account and add the API key/s

Navigate to Settings and Preferences:

Click into the Habitude Integration tab:

Select the school/trust from the dropdown and enter the key into the field:

Note: Save your changes each time you add a key

 

View the data being sent

Next to the field where you add your key, there's a button to view the data being sent. Here are details about the available data fields:

Candidate Title - The title added by the candidate to their application form

Candidate First Name - The first name added by the candidate to their application form

Candidate Last Name - The last name added by the candidate to their application form

Candidate Gender - The gender added by the candidate to their application form (please

note, candidates can select not to specify this)

Candidate Country - The country of residence added by the candidate to their application

form

Candidate Ethnicity - The ethnicity added by the candidate to their application form (please

note, candidates can select not to specify this)

Candidate Religion - The religion added by the candidate to their application form (please

note, candidates can select not to specify this)

Candidate Address - The address added by the candidate to their application form

Candidate Email Address - The email address that the candidate is registered with

Candidate Date of Birth - The date of birth added by the candidate to their application form

(please note, candidates can select not to specify this)

Job Role - The job title that was added to the vacancy when posted

Job Location - The address of the school/trust the job was posted under

Employer - The name of the school/trust

Personal Email Address - The email address that the candidate is registered with

Hiring Manager Name - Name of the user who posted the job

Hiring Manager Email Address - Email address of the user who posted the job

Advertised Job Role - The job title that was added to the vacancy when posted

Turn the integration on/off (this can be for certain schools only if relevant)

Next to the field where you added the key, there's a toggle switch to turn the integration on

or off. You can adjust this at any time:

Make sure to save any changes.

After pasting the API key and saving changes, you can now use the integration within Arbor Workflows.

Navigate back to Arbor Workflows and select the Workflows tab.

Whichever Arbor 2026 package you are using, we have a template ready for you to use to build the New Starter workflow ready to receive the data from MyNewTerm and create the new staff record in Arbor MIS. Your initial form will be triggered from MyNewTerm, so it must match a template that allows data to flow from MyNewTerm

The questions in the template trigger form match the MyNewTerm template and data fields listed above.

Once you have set up the template from the Template Library please contact us to make sure we are ready to receive data from MNT into the workflow.