Please ensure you have completed Step 1 before proceeding with the next steps.

Step 1 - Create your Slate Service Account

A. You can create a User ID and Password from the Active Users tab under Security Dashboard in Slate.

PLEASE NOTE: When creating your Slate Service Account, we recommend using an email address similar to [email protected]

B. To find the Slate Service Endpoint URL on the newly created Source Format page, navigate to Web Service and select View:

Important: When copying your Slate Service Endpoint URL, make sure the URL contains /manage/service/import. This confirms that you have copied the correct Web Services POST URL from Slate.

Step 2 — Send your Slate connection details to Unibuddy

Once Part 1 is complete, send the following information to your Unibuddy contact:

Slate Service Account User ID
Slate Service Account password
Slate Service Endpoint URL
Your preferred date format (dd-mm-yyyy, yyyy-mm-dd or mm-dd-yyyy)
If you're using the Slate Integration Client Task Tracker, please share this with us at the same time.

Step 3 — Unibuddy configures your test integration

Once we have received your connection details, we'll configure the integration in a test environment and create a test prospect.

The purpose of this initial test is to confirm that Unibuddy can successfully send prospect data to your Slate Source Format.

What is included in the initial test?

The initial generic test record contains standard Unibuddy prospect data.

Please note: The initial generic test record does not include university-specific custom fields.

This is because the test uses standard Unibuddy prospect data and is designed to confirm that a prospect can successfully reach Slate. Custom fields can be tested separately once the connection is confirmed.

Step 4 — Wait for the sample dataset

Unibuddy sends data to Slate at four scheduled sync times each day: 6am, 12pm, 6pm and 12am UK time.

Please allow until the next scheduled sync for your test data to arrive.

Once the sample has reached Slate, you should see it against your Unibuddy Source Format with a status similar to:

Awaiting activation of Source Format remap

Important: Do not activate Remapping before your sample data has arrived. The sample provides the incoming Unibuddy source fields you'll need to complete your mappings.

Step 5 — Confirm that the sample has arrived

Once the sample is visible in Slate, confirm with Unibuddy support that you can see the incoming Unibuddy fields.

Once you've confirmed receipt of the test record, you can begin mapping the incoming fields.

If the sample hasn't arrived after the next expected sync, contact Unibuddy Support so we can investigate further.

Step 6: Map the Unibuddy applicant ID

Before mapping the remaining fields, make sure you've created a unique person field in Slate for the Unibuddy ID.

The incoming Unibuddy applicant ID is:

applicant_id

In Remap, map the incoming applicant_id to the unique Unibuddy ID field you've created in Slate.

For full instructions, see:

👉 How do I map the Unibuddy applicant ID to a unique ID in Slate?

Step 7: Map the remaining Unibuddy fields

Open your Unibuddy Source Format in Slate and select Remap.

You can now map each incoming Unibuddy source field to the appropriate destination field in your Slate instance.

The fields you see are based on the fields included in your Source Format. Your Source Format determines which Unibuddy fields are sent to Slate, while your Slate configuration determines where those fields should be stored.

For each field:

Find the incoming Unibuddy source field.
Select the appropriate destination field in Slate.
Check that the mapping is correct.
Save your changes.

Can't see a field in Remap?

Check that:

The field is included in your Format Definition.
The field name is correct.
The test prospect has a value for that field.
Any custom field has been added correctly.

Need more help with Slate's Remap functionality?
For detailed guidance on how Slate field mappings and destination fields work, see Slate/Technolutions' Upload Dataset documentation. This explains how to select an incoming source field, assign its Slate destination, and configure Prompt Value Mappings where required.

Adding Community data

If your integration also needs to receive Community join interactions, follow our separate Community mapping guide:

👉 https://help.unibuddy.co/en/articles/6396089-how-do-i-add-community-join-interactions-to-a-user-record-timeline-in-slate

Step 8 — Activate Remapping

Once your sample data has arrived and you have completed your required field mappings, you can activate Remapping.

Before activating, make sure:

The Unibuddy applicant_id is mapped to your unique Unibuddy ID field.
Your required Unibuddy fields are mapped to the appropriate Slate fields.
You have reviewed your mappings and are happy with how the incoming data will be processed.

Then:

Open Edit Source Format.
Change Remap Active to Active.
Select Save.

Your Source Format is now ready to process new Unibuddy data using the mappings you've configured.

Important: Do not activate Remapping before your sample data has arrived and you have completed your mappings.

Step 9 — Test your completed mappings and confirm your test with Unibuddy

Once Remapping is active, we will create a new test prospect and wait until the next scheduled sync.

Check that:

The prospect arrives in Slate.
The expected fields are populated correctly.
The Unibuddy ID is populated correctly.
Any custom fields being tested are mapped correctly.

Once you've successfully received and checked the test prospect, let your Unibuddy contact know.

Please tell us whether:

The record arrived successfully.
The fields mapped correctly.
The prospect was created/matched as expected.

If you're using the Slate Integration Client Task Tracker, update the relevant testing steps there as well.

Step 10 — Go live 🎉

Once the test has been successfully completed and confirmed, Unibuddy can configure the integration for your live Unibuddy environment.

After the live configuration is enabled, eligible new or updated prospect records can be included in subsequent scheduled syncs.

We recommend checking the first live records received in Slate to confirm that the production configuration is behaving as expected.

Troubleshooting

I haven't received the sample after the next scheduled sync

First check:

Your Source Format is Active.
The Source Format uses JSON.
The documented Format Definition is still in place.
The root remains node="/".
SFTP access is OFF.
The Service Endpoint URL you provided to Unibuddy is the correct one.
The Slate Service Account is active.
You're checking the Source Format/environment configured for the test.

Then contact Unibuddy Support.

Please send us:

Your university name.
A screenshot of the affected Source Format.
A screenshot of what you see in Slate.

The sample arrived, but a field is missing

Check the Format Definition first.

A field needs to be correctly represented in the Source Format before it can be made available for mapping.

Also remember that the initial generic test prospect may not contain your institution-specific custom fields.

I changed my Service Account credentials

If your Service Account username or password changes after the integration has been configured, please contact Unibuddy Support.

The credentials used by the integration may also need to be updated before subsequent syncs can authenticate successfully.

Still having trouble?

Please contact Unibuddy Support and include:

Your university.
Whether the problem is happening in test or live.
The affected Slate Source Format.
Any error message shown by Slate.
Relevant screenshots.

Slate Setup Part 2 : Syncing with Unibuddy