HubSpot + Agile Education Marketing integration

Publishers and edtech companies that sell to schools license Agile’s data to learn which districts and schools exist and who works in them this year. Agile Education Marketing, which now brands itself AgileED, compiles records on public, private, parochial and charter K-12 schools and districts and the educators in them, alongside higher education, early childhood and public libraries. It puts the sector’s annual attrition at 20 to 25 percent, so a list bought once drifts further from the truth every month.

HubSpot adds a problem of its own. It treats a company’s domain as the identifier that prevents duplicates, and Agile’s own guidance notes that schools commonly use their district’s email domain, and that almost all schools in South Dakota share one. Matching on that domain, HubSpot files teachers from many schools under a single company, and a territory plan counts one account where the district has many.

Agile offers two ways into the portal. AgileConnect for HubSpot matches your companies and contacts to Agile’s records every week and appends the fields you licensed. The Look-Up API completes a form with Agile’s education data while someone fills it in. Most teams should start with the first. What we add sits around it: the district above each school, the form that must know the school at submission, and the standard properties your sales team reads.

Three Agile records matter in HubSpot. Institutions, meaning schools and districts, become companies. Personnel, the educators and administrators in them, become contacts. The link between a district and its schools becomes HubSpot’s parent and child company association, which allows many schools under a district and one district above each school.

Everything moves one way. Agile owns the reference record and rebuilds it weekly; HubSpot owns the relationship, the deal and the activity. AgileConnect writes only the custom properties it creates at install, grouped as AgileConnect, and touches standard properties only when its prospecting tool creates a record. Where you want an Agile value in a standard field, a HubSpot workflow copies it, as Agile’s FAQ suggests.

The keys are Agile’s Institution UID for a company and its Personnel UID for a contact. The obvious keys fail: a domain is shared across a district, and school names repeat from one district to the next. AgileConnect appends the UIDs to every record it matches. In any build of ours, the Institution UID also sits in a property that requires unique values, so no second company can claim the same school.

Two runtimes share the portal. The first is Agile’s. Once your admin authenticates AgileConnect, Agile’s integrations team schedules three jobs: a weekly match of every company and contact, a nightly match on the other weekdays for unmatched records created or changed recently, and a weekly update of the Agile properties. Monday’s nightly run looks back 72 hours to cover the weekend. A failed job retries three times with growing delays before Agile’s team is alerted.

The second runtime is ours, built only where a form must know the school at submission. The form queries the Look-Up API through a small proxy we host, so no Agile credential reaches the browser, and writes the chosen institution’s UID into a hidden field. HubSpot sends a webhook when that contact property changes, and the event joins a queue. A consumer upserts the district, then the school, on the unique UID property, links them as parent and child, and makes the school the contact’s primary company. Every write is keyed, so a replayed event changes nothing. The house name for this shape is a webhook queue.

Timing settles the route here: when HubSpot has to know the school. If the next morning is soon enough, AgileConnect handles matching, enrichment and prospecting without a build, which is why we recommend it. If a form must identify the school at the moment of submission, or districts must sit above their schools, a custom API integration adds that beside AgileConnect rather than replacing it.

We steer away from an iPaaS here. The Look-Up API does its work inside the form, before anyone submits, while an automation platform starts from the submission, by which point AgileConnect’s nightly match is already on its way. Agile’s integrations page lists Salesforce, HubSpot and Marketo and no iPaaS, so every step would be hand-built anyway.

1. Scope. We list which Agile licences you hold (institution, personnel, premium), the fields you picked from Agile’s data dictionary, and any form that must name the school at submission.
2. Architect. We fix the Institution UID as the company key, districts above schools, the domain setting, and which Agile values workflows copy into standard properties.
3. Build. Your admin authenticates AgileConnect in a HubSpot sandbox first, with a sandbox instance Agile creates on request. Where the form route is in scope, the proxy and the consumer are built there too.
4. Validate. We confirm Agile properties populate on sample records, prospect a handful with the licence box checked, and list any companies sharing a UID.
5. Operate. We watch the weekly jobs, clear the duplicates Agile’s UIDs expose, and retest after each entry in Agile’s What’s New log that touches a job.