How a college or university that runs admissions in Slate can connect it to HubSpot, where continuing education, executive education, events, alumni and corporate partnership teams work: shared person records, inquiry routing between the two, application status for cross-unit nurturing, and consent that holds in both systems.
Slate is the CRM many admissions offices run, from first inquiry through decision release. Other units on the same campus (continuing and executive education, events, alumni relations, corporate partnerships) often run HubSpot. The same person can be a prospect in both, so the two systems need to share records without fighting over them.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Configured inside Slate by an administrator, who grants web service permission per query and creates the import service account.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Slate shares data through queries and imports, so admissions keeps Slate and every other unit works from HubSpot, with one agreed owner for each record.
Campaign Creators assessment
Slate does not publish a fixed set of REST resources. Instead, any Configurable Joins query can be published as a web service that returns JSON, XML, Excel or CSV, or scheduled to push JSON or XML to a remote endpoint. Data comes into Slate through source formats: files or posts land in Upload Dataset, pushed to a Slate endpoint, pulled by Slate from a remote URL, or picked up by SFTP. A Slate administrator builds the queries and source formats; CC designs them and builds everything on the HubSpot side. Neither HubSpot nor Technolutions publishes a HubSpot app for Slate, so this is a direct build. Slate processes most imports within 15 minutes, so routing between the systems runs in minutes, not seconds.
Ratings are CC judgments from Technolutions' and HubSpot's public documentation. Queries, source formats and custom fields differ per Slate database and are confirmed with the client's Slate administrator in discovery.
The admissions office decides exactly which fields leave Slate by building the query, and can restrict each web service to a token, a service account and allowed networks.
Imports run in batches (50 posts per five minutes, most processed within 15 minutes). Slate matches people on its GUID, Slate ID, external ID or name with email, so HubSpot's ID is stored in Slate to keep matches exact.
Each unit agrees who owns a person, which application facts other units may see, and how opt-outs travel. The registrar and counsel confirm FERPA treatment before any build.
Seven building blocks shape the integration. Five carry it, one supports the initial load, and one is a scope decision about consent.
A Slate query published as an endpoint. The integration calls it with parameters, such as the time of the last run, to read only what changed.
Slate runs a query in a chosen delivery window and posts the result as JSON or XML to an endpoint CC hosts.
A source format defines how incoming rows map to Slate fields. HubSpot-side records are posted in batches to the source format's endpoint.
Slate matches incoming person data on its GUID, Slate identity, unique custom fields, external ID or Slate ID, then first, last and email, then first, last and birthdate.
Inquiry forms and event registrations are Slate forms. Each response is kept as a form registration and shown on the person's timeline, with interactions recording other activity.
Technolutions recommends SFTP for sending data outside Slate. Files suit the initial load and nightly reconciliation.
Slate's Opt Out tag stops non-transactional email. Slate removes it when the person submits a person-scoped form or starts an application. Decide how opt-outs in each system affect the other.
Slate and HubSpot each keep their own records. A CC-built integration layer reads changed data from Slate's query web services, decides which unit owns each person and inquiry, matches records, and writes to HubSpot in batches. HubSpot-owned inquiries and consent travel back to Slate in batches through a source format.
Admissions owns the applicant and the application in Slate. Other units own their programs, events and relationships in HubSpot. Each shared field has exactly one system that may change it.
Reading, decisions and decision release stay in Slate. HubSpot receives status and released outcomes, never application content.
Every unit's activity with a person meets on one HubSpot record, so leaders see the whole relationship across programs.
Each phase ends on a gate the institution signs off before the next begins. The ownership agreement comes first because both systems will hold the same people.
Map the units on each system, the shared audiences and the use cases. Agree who owns each person, which application facts other units may see, and how inquiries route. Confirm FERPA treatment with the registrar.
The Slate administrator, with the Administrator (All Access) role, creates a service account, grants Web Service permission on the agreed queries and sets allowed networks. CC creates a HubSpot private app.
Specify the export queries (persons, applications, forms, interactions, opt-outs) with a last-run parameter, and the source format that receives HubSpot data. The Slate administrator builds or approves them.
Create properties, the Application custom object, association labels, unit pipelines and property groups in a HubSpot sandbox.
Build the change reader, routing rules, identity resolver, opt-out handling, the batch poster with callbacks, and an error replay queue.
Load shared persons and current applications by SFTP or a one-time query export, and write HubSpot IDs back to Slate.
Build routing, nurturing and event automations with sends paused, run two weeks in parallel, then switch on.
Slate field names come from each institution's queries and source formats, so the export names shown here describe the data. Exact names are set when the queries are built in discovery.
| Slate field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Person records | ||||
| Slate GUID | slate_guid | Contact | Slate → HS | Primary Slate key. Unique. |
| Slate ID | slate_id | Contact | Slate → HS | Shown to staff for lookups. |
| First and last name | firstname, lastname | Contact | ↔ Both | Owner set per field in the ownership table. |
| Contact | ↔ Both | Match key after IDs. | ||
| Phone | phone | Contact | ↔ Both | |
| City, region, country | city, state, country | Contact | Slate → HS | Slate owns the applicant's address. |
| HubSpot record ID | hs_object_id | Contact | HS → Slate | Stored in a unique person-scoped Slate field for exact matching. |
| Tags (agreed set) | slate_tags | Contact | Slate → HS | Only tags other units should act on. |
| Applications | ||||
| Application GUID | slate_application_id | Application | Slate → HS | Primary key. Unique. |
| Round | slate_round | Application | Slate → HS | For example early decision, regular decision, transfer. |
| Period | slate_period | Application | Slate → HS | Active or inactive application period. |
| Application status | slate_app_status | Application | Slate → HS | Awaiting Submission, Awaiting Payment, Awaiting Materials, Awaiting Confirmation, Awaiting Decision, Decided. |
| Released decision | slate_decision | Application | Slate → HS | Only after release, and only if admissions agrees. |
| Program of interest | slate_program | Application | Slate → HS | Confirm the field in discovery. |
| Application to person | Association | Application ↔ Contact | Slate → HS | One person can hold several applications. |
| Inquiries, forms & events | ||||
| Request for information response | Custom event: Slate inquiry | Contact | Slate → HS | Logged on the HubSpot timeline. |
| HubSpot inquiry for an admissions program | Source format row (person + interaction) | Contact | HS → Slate | Routed to Slate when admissions owns the program. |
| Slate inquiry for a HubSpot-owned program | Contact + Deal | Deal | Slate → HS | Routed to the owning unit's pipeline. |
| Event registration and attendance | Marketing event attendee | Marketing event | Slate → HS | Registrations, cancellations and check-ins. |
| HubSpot event registration | Source format row (interaction) | Contact | HS → Slate | Optional. Lets admissions see campus events. |
| Interactions (agreed codes) | Custom event: Slate interaction | Contact | Slate → HS | Only interaction codes on the agreed list. |
| Consent & opt-outs | ||||
| Opt Out tag | slate_opt_out | Contact | Slate → HS | Applied to the agreed HubSpot subscription types. |
| HubSpot unsubscribe | Opt Out tag | Contact | HS → Slate | Set through Upload Dataset. |
| Opt Out removed by a new form or application | slate_opt_out_cleared | Contact | Slate → HS | Flags for review; HubSpot opt-outs are not reversed automatically. |
| Cross-unit activity | ||||
| Continuing or executive education enrollment | Source format row (interaction) | Deal | HS → Slate | Optional. Shows admissions other relationships. |
| Alumni or partnership affiliation | slate_affiliation | Contact | HS → Slate | Optional. Confirm the field in discovery. |
Values Technolutions publishes are stated; anything specific to the institution's Slate database is marked for confirmation.
| Topic | Slate | HubSpot |
|---|---|---|
| Access model | Configured in Slate by a user with the Administrator (All Access) role, who grants Web Service permission per query and creates the service account for imports. | Private app access token or OAuth public app, scoped per object. Custom objects need an Enterprise subscription. |
| Interfaces | Export: query-based web services (JSON, XML, Excel, CSV) and scheduled pushes to a remote web service (JSON or XML). Import: source formats through Upload Dataset, by push, pull or SFTP. | REST APIs: CRM objects, associations, custom events, marketing events, subscriptions. |
| Authentication | Export: a user token passed as the h parameter, or a username and password plus the token; optional allowed networks. Import: service account with Basic authentication or a client certificate. | Bearer token on every call. |
| Freshness | Uploads appear in Upload Dataset at once; most are processed within 15 minutes. Pull imports default to every 24 hours, with a 60-minute minimum. Scheduled pushes run in a delivery window. | Writes are immediate; batch endpoints handle volume. |
| Rate limits | Web services: 300 requests and 300 seconds of processing per database in any five-minute interval. Import posts: 50 per five-minute window. | Per-10-second burst and daily limits by subscription tier. |
| Change detection | No record-level push events. Parameterized queries read changes since the last run; scheduled pushes send on a timetable. | Webhooks for HubSpot-side changes. |
| Sensitive data | Applicant and student data. Birthdate is used for matching in Slate and is never sent to HubSpot. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
An applicant can also be an event guest or an executive education prospect. Without a signed ownership table both systems overwrite each other. Each shared field gets one owner, and the other system reads it.
FERPA protects education records once a person is in attendance, and many institutions apply the same care to applicants. The registrar and counsel confirm what application facts other units may see, and the SOW names that approval as a dependency.
Slate accepts 50 import posts per five minutes and processes most uploads within 15 minutes. The integration batches HubSpot changes and uses Slate's callback to confirm each import.
Slate's Opt Out tag covers non-transactional email and is removed when a person submits a new form or starts an application. The rules for carrying opt-outs each way are agreed per subscription type.
Queries and source formats are built inside Slate by someone with full administrator rights. CC writes the specifications, but the client's Slate team must build or approve them, so their time is a dependency in the plan.
Slate also serves alumni and advancement. If the institution runs advancement in Slate, alumni ownership is decided in discovery before any alumni data moves.
Each inquiry reaches the team that owns the program, whichever system it arrived in, with source and interest attached.
With policy approval, applicants who decide not to enroll can be offered continuing education, summer or executive programs, and HubSpot sends only what the agreed rules allow.
Admissions status, event attendance, program enrollments and partnership activity meet on one HubSpot record for every unit that needs it.
Campus events run in either system appear on the same person, so follow-up is coordinated rather than duplicated.
An opt-out recorded in one system is honored in the other, by the rules each unit agreed.
Leaders see inquiries, applications, program enrollments and partnerships in one set of HubSpot dashboards.
The integration does not move admissions out of Slate. It lets each unit run its own system while sharing the people they have in common, under rules every unit has signed.
All custom properties use the slate_ prefix in a Slate property group. Application data sits on an Application custom object so one person can hold several applications.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| slate_guid | Slate GUID | Contact | Single-line text | Slate person GUID; unique |
| slate_id | Slate ID | Contact | Single-line text | Slate ID shown to staff |
| slate_tags | Slate Tags | Contact | Multiple checkboxes | Agreed tag list only |
| slate_opt_out | Slate Opt Out | Contact | Single checkbox | Opt Out tag present |
| slate_opt_out_cleared | Slate Opt Out Cleared | Contact | Date picker | When Slate removed the tag |
| slate_owner_unit | Owning Unit | Contact | Dropdown | From the ownership rules |
| slate_application_id | Application GUID | Application | Single-line text | Slate application GUID; unique |
| slate_round | Round | Application | Dropdown | Application round |
| slate_period | Period | Application | Dropdown | Application period |
| slate_app_status | Application Status | Application | Dropdown | Slate application status |
| slate_decision | Released Decision | Application | Dropdown | Released decisions only |
| slate_program | Program | Application | Dropdown | Program of interest |
Choose the record types and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation from Technolutions and HubSpot. Each item marked for confirmation is verified with the institution's Slate administrator during discovery.
Yes, through a direct build on Slate's web services. A Slate administrator publishes Configurable Joins queries as web services that return JSON, XML, Excel or CSV, and HubSpot data comes back into Slate through a source format. Neither HubSpot nor Technolutions publishes a HubSpot app for Slate, so Campaign Creators designs the queries and builds everything on the HubSpot side.
Slate persons, application status and released decisions, form and event registrations, interactions and opt-outs flow to HubSpot contacts, an Application custom object and marketing events. HubSpot sends routed inquiries, its contact IDs, opt-outs and cross-unit activity back to Slate in batches.
Admissions owns the applicant and the application in Slate, and reading, decisions and decision release stay there. Other units own their programs, events and relationships in HubSpot. Each shared field has exactly one system that may change it, and HubSpot receives application status, never application content.
Seven phases, each closed by an institution sign-off: discovery and an ownership agreement (with FERPA treatment confirmed by the registrar), access, query and source format design, the HubSpot data model, the build, a backfill, and a two-week parallel run before automations are switched on.
Timeline and cost depend on the units and flows in scope, the queries and source formats needed, and the consent rules. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.