Before you start
Before testing, make sure you've completed Parts 1–3.
You should have:
Created and saved your Power Automate flow.
Configured When an HTTP request is received.
Added Parse JSON and the Unibuddy data schema.
Sent your HTTP POST URL and required date format to Unibuddy Support.
Configured how existing prospects are identified.
Configured your Create and Update CRM actions.
Mapped the Unibuddy fields you want to store in your CRM.
Saved your flow and made sure it is turned on.
Once these steps are complete, you're ready to test the integration.
What you'll do across this guide series
The full setup is split into three stages:
Part 1 — Receive Unibuddy data in Power Automate
Create your flow, configure the HTTP trigger, add Parse JSON and the Unibuddy data schema, and send your HTTP POST URL to Unibuddy.
Part 2 — Check, create and update prospects in your CRM
Configure Power Automate to identify existing prospects and determine whether to update an existing CRM record or create a new one.
Part 3 — Map Unibuddy data to your CRM
Choose which Unibuddy data you want to store and map it to the appropriate fields in your CRM.
Part 4 — Test your integration and go live ← You are here
Test the complete integration, verify the data received by your CRM, troubleshoot any issues and work with Unibuddy to move your integration to your live university environment.
This article covers Part 4.
Step 1: Unibuddy will configure your test connection
Before your integration is connected to your live university environment, Unibuddy will first configure the HTTP POST URL you provided against a test university environment.
Unibuddy Support will then create a test prospect so that sample prospect data can be sent through your Power Automate flow.
This lets you check the complete process before the integration is enabled for your live university.
Once you have completed Parts 1–3 of the integration steps, email [email protected] to let us know that you'd like to run a final test before going live.
Unibuddy CRM data is sent during scheduled sync windows.
The scheduled sync times are:
12AM, 6AM, 12PM and 6PM UK time
Once Unibuddy Support confirms that your test connection and test prospect have been configured, allow the next scheduled sync window to pass.
📝 Important: Receiving a successful test does not mean your integration is live. Your live university environment will only be configured after you've checked the test and confirmed that you're happy to proceed.
Step 2: Check your test and confirm you're happy with the result
Once the next scheduled sync has passed, review the test from beginning to end.
The purpose of this check is simply to make sure that the data has successfully travelled through:
Unibuddy → Power Automate → your CRM
1. Check Power Automate
Open your Power Automate flow and review the relevant run in your 28-day run history.
Check that:
A run was triggered for the Unibuddy test.
When an HTTP request is received completed successfully.
Parse JSON completed successfully.
The flow followed the expected Create or Update path.
The CRM action completed successfully.
There are no unexpected failed actions or error messages.
2. Check your CRM
Next, find the test prospect in your CRM and check that:
The test prospect has been created or updated as expected.
The prospect appears in the correct CRM record type/table.
First name, last name and email appear in the correct fields.
The other Unibuddy fields you've chosen to map appear in the intended CRM fields.
Dates appear in the expected format.
Areas of study and any other fields containing multiple values appear where you expect them.
Marketing consent and other fields important to your organisation contain the expected values.
No unexpected duplicate prospect has been created.
The overall record looks correct based on the mappings you configured in Part 3.
📝 Custom fields: Your university-specific custom fields won't appear in the initial test data because the Unibuddy test university doesn't have your university's custom fields configured. You'll be able to verify these once data is being sent from your live university environment.
If everything looks correct
If everything looks correct
If you're happy with the test result, reply to Unibuddy Support and confirm that:
You've received the test successfully.
The Power Automate flow completed successfully.
The prospect appeared correctly in your CRM.
You're happy with the field mappings.
You're ready for the integration to be moved to your live university environment.
If something doesn't look right
If something doesn't look right
If the test hasn't worked as expected, don't confirm that you're ready to go live yet.
First, identify where the issue occurred:
What happened | What to check |
No Power Automate run appeared | Flow is turned on, correct Power Automate environment, next scheduled sync has passed |
HTTP request failed | When an HTTP request is received action and its error details |
Parse JSON failed | Parse JSON error and the data received by the action |
CRM Create/Update action failed | CRM connection, required fields, mappings and error message |
Flow succeeded but a CRM field is empty/wrong | Compare the incoming Unibuddy value with the mapping configured in Part 3 |
Duplicate prospect was created | Review your Unibuddy ID ↔ CRM ID matching setup from Part 2 |
Custom field isn't in the initial test | The test university doesn't contain your university-specific custom fields |
If you need help, contact Unibuddy Support with the test prospect details, approximate time of the test, and screenshots of the relevant Power Automate run and any error messages.
Step 3: Going live
Once you've confirmed that you're happy with the test, Unibuddy Support can configure the integration for your live university environment.
We'll let you know when the live configuration has been completed.
After this, we recommend checking the first prospect that passes through the live integration to make sure the complete journey continues to work as expected with your university's data.
At that point, you can also verify any university-specific custom fields that weren't available in the initial test.