Arbor can integrate with a large number of third-party applications, and our current integrations are listed below.
We'd recommend contacting the third-party company directly if you have any queries around what their Arbor integration allows for within their software.
In Use: At least one Arbor school is actively using this integration.
Integrated: The partner has an integration with Arbor (potentially via a Data Provider), but we cannot confirm whether it is currently in use.
Implementation: Either Arbor or the partner is currently working on developing an integration.
On Roadmap: We are planning on working on an integration with this partner as part of our scheduled Product Roadmap work.
In discussion: We're currently speaking to the company around potentially integrating.
Contacted - No integration planned: We've been in touch with the company, and they've told us that at this point they don't have any plans to integrate with Arbor.
API: We have a direct API connection with the partner.
MIS Feature: We have a built-in feature within Arbor that enables data to be shared with the partner (this may be a manual export).
Sync via 'x' e.g. Sync Via Wonde or Groupcall: Our link with the partner is provided by the listed third-party.
Sync via Data Provider: We have a link with the partner, but you'll need to confirm with them the exact third-party they are using to extract data from Arbor.
CRW: You'll need to create a Custom Report in Arbor to export data, in order to import this into the partner's software.
CTF Export: You'll need to export a CTF file from Arbor in order to import student data into the partner's software.
A one-way integration only permits the movement of data in one direction. The data will be extracted from Arbor by the integrated partner - no information will be put into Arbor from the third party application. All integrations that are synced by Assembly, Groupcall and Wonde are one-way integrations.
A two-way integration allows data to flow in both directions - from Arbor to the third party, and into Arbor from the third party application. You'll be able to view the specific write (update) and/or delete access that the application has to your Arbor data before you approve the integration.
When setting up an integration, you'll see if an application wants to 'read' or 'write' data.
A read integration means the third party application pulls information from Arbor, to make use of this within their software:
- The third party application chooses what information to pull out of Arbor.
- Any changes to the information being read need to be made by the third party application - please contact them if you're unsure on what information is being pulled.
- If an application has a read integration, no information will be edited in Arbor.
- Changes are made in the third party application and pushed into Arbor.
- We will have developed the write integration with the third party application - if you'd like to change what information is written back to Arbor, please contact the third party application. They will contact us if changes are needed.
For both types of integrations, the sync frequency is determined by the third party application - please contact them for information on how often syncs of data occur.
If you'd like to integrate your Arbor site with a company/partner that has the Integration Type of API or Sync via..., you should contact the company in the first instance to let them know you are using Arbor and that you'd like to set up the integration. You can then follow the instructions in this article to move through the setup process.
If a company isn't displayed on the list below, we've not had any contact with them regarding an integration. If you'd like a company or application to integrate with us, but can't find them on the list, please direct them to this article: How can we set up our own API Integration with Arbor?