Integration Products | Campaign Creators

Canvas LMS HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:05:34 PM
Integration Assessment
Integration Assessment · Education

Canvas LMS × HubSpot

How continuing education units, professional learning businesses and universities can bring Canvas enrollments, course progress, completions and certificates into HubSpot, so marketing, sales and learner success teams see what each learner is doing and can act on it, and how a closed deal in HubSpot can enroll a learner in Canvas.

Learning managementCanvas REST APILive EventsCanvas Data 2Canvas Catalog APICustom build
Platform ownerInstructure
Integration typeCustom build on Canvas APIs and Live Events
Primary directionCanvas → HubSpot
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Canvas integrate with HubSpot?

Canvas is Instructure's learning management system. It records who is enrolled in which course, how far they have progressed, whether they completed, and, through Canvas Catalog, what they bought and which certificates they earned. HubSpot is where the business that sells and supports that learning runs its marketing, sales and renewals.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The REST API is documented publicly. The institution's Canvas admin issues a developer key.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Canvas pushes enrollment and completion events as they happen, so HubSpot can act on learning activity the same day.

Campaign Creators assessment

Canvas exposes a well-documented REST API with OAuth 2.0, a Live Events stream that posts enrollment, course progress, completion and grade events to an HTTPS endpoint or a queue, and Canvas Data 2 for bulk history. Institutions that sell courses through Canvas Catalog add the Catalog API, which covers catalog courses, programs, orders, enrollments and completed certificates. CC builds a sync module that turns these into HubSpot contacts, a course catalog, enrollment records and revenue, and lets HubSpot enroll a learner when a deal closes. The main decision is privacy: for degree students, course records are education records, so the institution decides which learning signals HubSpot may hold.

Scorecard
Event coverageHigh
API accessAdmin-issued
Public docsExtensive
Build complexityModerate

Ratings are CC judgments from Instructure's public developer documentation. Event subscriptions, Catalog licensing and developer key settings are confirmed against the client's Canvas instance during discovery.

Strength

Completion events arrive as they happen

Live Events include enrollment_created, enrollment_updated, course_progress and course_completed, with the learner's email and requirement counts, so HubSpot does not wait for a nightly report.

Plan for

Events can arrive twice or out of order

Instructure documents that Live Events delivery is not ordered and can repeat. The sync module reads the current enrollment from the REST API before writing, so a late event cannot overwrite newer data.

Gate

Privacy rules come first

For credit-bearing students, course activity is part of the education record under FERPA. The registrar or privacy lead signs off which fields reach HubSpot, and grades stay out unless approved.

02 — API modules

Which Canvas APIs does the integration use?

Seven parts of Canvas matter to HubSpot. Four carry the integration, two support it, and one is a privacy decision the institution makes.

Integration path

Canvas REST API

OAuth 2.0 · developer keys

Users, courses, sections and enrollments, read and written with an OAuth token issued against a developer key the institution's Canvas admin creates.

  • GET /api/v1/courses/:course_id/enrollments
  • POST /api/v1/courses/:course_id/enrollments for write-back
  • Cost-based throttling with remaining quota in response headers
Core

Live Events

HTTPS or SQS · Canvas or Caliper format

Canvas posts selected events to an endpoint CC hosts, in Canvas JSON or the IMS Caliper format, with an option to sign each payload as a JWT.

  • Enrollment, course, grade, submission and user events
  • Endpoint must answer within 15 seconds
  • Failed deliveries retried up to six times
Core

Enrollments & completion

enrollment_* · course_progress · course_completed

Enrollment state for each learner in each course, progress through module requirements, and the moment a course is completed.

  • States: active, invited, completed, inactive, deleted
  • Requirement count and completed count
  • Completion time from progress.completed_at
Core where licensed

Canvas Catalog

Catalog API · storefront, orders, certificates

The storefront many continuing education teams use to publish courses and programs, take registrations and payments, and issue certificates.

  • Catalog courses, programs and enrollments
  • Orders for paid registrations
  • Completed certificates per learner
Enrichment

Engagement signals

last_activity_at · total_activity_time · scores

Last activity, total time in course and current score show who is engaged and who is drifting, for renewals and learner success outreach.

  • Activity rolled up per learner
  • Scores only where approved
  • Feeds HubSpot lists and health views
Backfill

Canvas Data 2

DAP API · snapshot and incremental

Bulk access to Canvas tables through Instructure's Data Access Platform. Used once to load history, and for reconciliation checks.

  • Client ID and secret from Instructure Identity Services
  • Full snapshot, then incremental changes
  • JSONL output loaded by the integration layer
Scope decision

Learner records in HubSpot

FERPA · institution decision

For degree-seeking students, enrollments, scores and submissions are education records. The institution decides what HubSpot may hold; non-credit learners may follow different rules.

  • Separate rules for credit and non-credit learners
  • Status flags rather than grades
  • Written field list in the SOW
03 — Framework

How does the Canvas HubSpot integration work?

Canvas sends Live Events to a CC-hosted endpoint. The integration layer checks the signature, reads the current record from the REST API, matches the learner, applies the privacy rules and writes to HubSpot. HubSpot workflows call back into Canvas or Catalog to enroll learners.

Canvas LMS
Live Eventsenrollments, progress, completions
Canvas REST APIusers, courses, enrollments
Canvas Catalog APIcatalog courses, orders, certificates
Canvas Data 2history for backfill
CC integration layer
Event receiverJWT check, queue, de-duplication
Record fetchercurrent state from the REST API
Identity resolveremail · SIS user ID · Canvas user ID
Privacy filterdrops fields the institution excludes
HubSpot writer & enroll bridgebatch upserts; deal won → enrollment
HubSpot
Contacts & companieslearners and their employers
Courses objectone record per Canvas or Catalog course
Course enrollments (custom object)status, progress, completion, certificate
Orders & dealsCatalog revenue, group and renewal deals
Lists, workflows & reportsonboarding, nudges, upsell, renewals
Canvas → HubSpot (primary flow)HubSpot → Canvas (enrollments and new users when a deal closes)
Principle

Canvas owns the learning record

Enrollment state, progress, completion and scores are official in Canvas. HubSpot reads them and never edits them.

Principle

HubSpot owns the relationship

Inquiries, purchases outside Catalog, account ownership and renewals live in HubSpot. A won deal is what tells Canvas to enroll someone.

Principle

Read before you write

Every event is checked against the current REST API record, so repeated or out-of-order events cannot write stale data.

04 — Process

What does Canvas HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Enrollments and completions go live first, then Catalog revenue and write-back.

1

Discovery & privacy rules

List the Canvas accounts, course types and learner groups in scope, whether Canvas Catalog is licensed, and which teams use HubSpot. Agree with the registrar or privacy lead what learner data HubSpot may hold.

Gate to next phaseSigned privacy memo and field list
2

Canvas access

The Canvas admin creates a developer key, authorizes the integration user, sets up the Live Events subscription to CC's endpoint, and issues Catalog and Canvas Data 2 credentials if in scope.

Gate to next phaseTest events and API calls received
3

Identity & ownership rules

Agree how learners match (email, then SIS user ID), how courses map to HubSpot course records, and which system owns each field.

Gate to next phaseSigned match rules and ownership matrix
4

HubSpot data model

Activate the Courses object, create the Course Enrollment custom object, association labels, order and renewal pipelines and the Canvas property group in a sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the event receiver, record fetcher, identity resolver, privacy filter, HubSpot writer and enroll bridge, with idempotent writes and an error replay queue.

Gate to next phaseEnrollments, completions and write-back working in sandbox
6

Backfill

Load course catalog and enrollment history for an agreed window from Canvas Data 2 or the REST API, then compute learner rollups once.

Gate to next phaseEnrollment and completion counts reconcile to Canvas reports
7

Workflows, parallel run & launch

Build onboarding, progress nudges, completion follow-up and renewal workflows with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Canvas HubSpot integration sync?

Field names follow Instructure's public REST API, Live Events and Catalog API documentation. Exact payloads are confirmed against the client's Canvas instance during the access phase.

Canvas fieldHubSpot propertyObjectDirectionNotes
Learners · contacts
user.email (Live Events) / user loginemailContactCNV → HSMatch key, then SIS user ID.
user.idcnv_user_idContact↔ BothStored so write-back can enroll the same user.
sis_user_idcnv_sis_user_idContactCNV → HSOnly visible with SIS permission.
user.namefirstname, lastnameContactCNV → HSFill blanks only; HubSpot edits stay in HubSpot.
New learner from HubSpotCanvas or Catalog userUserHS → CNVCreated when a deal closes and no user exists. Confirm account permissions in discovery.
Courses · catalog
course.id, nameCourse record (hs_course_name)Courses objectCNV → HSOne record per Canvas course.
sis_course_idcnv_sis_course_idCourses objectCNV → HSLinks courses to the institution's SIS.
course.account_idcnv_account_idCourses objectCNV → HSSeparates departments or sub-accounts.
Catalog course or programcnv_catalog_programCourses objectCNV → HSFrom the Catalog API courses and programs.
Enrollments & completion
enrollment.idcnv_enrollment_idCourse EnrollmentCNV → HSUnique key on the custom object.
enrollment_state / workflow_statecnv_enrollment_stateCourse EnrollmentCNV → HSactive, invited, completed, inactive, deleted.
typecnv_enrollment_typeCourse EnrollmentCNV → HSStudent, teacher, observer. Teachers can sync to an instructor list.
progress.requirement_completed_count / requirement_countcnv_progress_pctCourse EnrollmentCNV → HSComputed percent from course_progress.
progress.completed_atcnv_completed_atCourse EnrollmentCNV → HSFrom course_completed.
last_activity_atcnv_last_activity_atCourse EnrollmentCNV → HSRead from the Enrollments API.
total_activity_timecnv_total_activity_minutesCourse EnrollmentCNV → HSSeconds converted to minutes.
grades.current_scorecnv_current_scoreCourse EnrollmentCNV → HSOnly where the institution approves. Off by default.
count of completed enrollmentscnv_courses_completedContactCNV → HSComputed in the integration layer.
Catalog revenue & certificates
Catalog orderOrderOrderCNV → HSPaid registrations; confirm order fields in discovery.
Catalog order itemsLine itemsLine itemCNV → HSOne per course or program purchased.
Completed certificatecnv_certificate_earned, cnv_certificate_dateCourse EnrollmentCNV → HSFrom the Catalog completed certificates endpoint.
Closed-won dealenrollment (POST)EnrollmentHS → CNVEnrolls the learner in the purchased course or Catalog listing.
06 — Auth & API

How are authentication and API limits handled?

Canvas access is issued by the institution's Canvas admin. Values Instructure does not publish are marked for confirmation.

TopicCanvasHubSpot
AuthenticationOAuth 2.0 against a developer key issued by the institution's Canvas admin. Access tokens last one hour and are renewed with the original refresh token. Applications used by more than one person must use OAuth, not manual tokens.Private app access token or OAuth 2.0 public app, scoped per object.
InterfacesCanvas REST API (/api/v1/: users, courses, sections, enrollments), Canvas Catalog API (courses, programs, enrollments, orders, completed certificates), and Canvas Data 2 through the DAP API.REST APIs: CRM objects, Courses object, custom objects, commerce objects, associations.
Live EventsDelivered to HTTPS (each event a POST, optionally signed as a JWT with keys published at a JWKS endpoint) or to an SQS queue, which cannot be FIFO. Canvas or Caliper IMS format.HubSpot signs its own webhooks with a v3 signature.
Delivery behaviorThe endpoint must return a 2xx within 15 seconds. Failures are retried up to six times, then recorded as failed. Delivery is not ordered and can repeat.Client retries with backoff on 429.
Rate limitsCost-based quota that refills over time. Each response carries X-Request-Cost; throttled requests return 429. One request at a time is unlikely to be throttled. Exact quota: not published. Confirm with Instructure.Per-10-second burst and daily limits by subscription tier.
Bulk dataCanvas Data 2 credentials (client ID and secret) are created in Instructure Identity Services. Snapshot once, then incremental queries.CRM imports and batch endpoints for large loads.
Catalog API accessRequires a Canvas Catalog license. Token setup: confirm with Instructure.Orders and line items available on all hubs; custom objects need Enterprise.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Learner privacy for degree studentsHigh

Course activity for credit-bearing students is part of the education record. The institution decides which fields HubSpot holds, and grades stay off unless approved in writing.

Events can repeat or arrive lateHigh

Live Events are not ordered and may be delivered more than once. The sync module de-duplicates by event and reads the current enrollment before every write.

Learners without a usable emailMedium

Some institutions use SIS IDs or login IDs rather than personal emails. Match rules run email first, then SIS user ID, and unmatched learners go to a review list.

Catalog may not be licensedMedium

Orders and certificates come from Canvas Catalog. Without it, revenue comes from HubSpot deals or another payment record, and completion is taken from Canvas course completion.

Course completion depends on course designMedium

Canvas measures progress and completion against module requirements. Courses built without requirements need a completion rule agreed per course, such as a final score or end date.

Endpoint must stay healthyLow

Canvas can deactivate a Live Events subscription after a large number of failures. The receiver queues events before processing and alerts on errors, so it always answers within 15 seconds.

Opportunities in HubSpot

Upsell on completionHigh value

A completed course triggers the next course, program or certification offer, timed to the learner's actual progress.

Renewals backed by usageHigh value

Account managers see how many of a client's learners enrolled, progressed and completed, so group contracts renew on evidence.

Enrollment from a closed dealHigh value

When a deal is won, HubSpot enrolls each learner in the right course, so onboarding starts the same day without manual admin.

Progress nudgesMedium value

Learners who stall get reminders and a check-in from learner success before they drop out.

Certificates as proof pointsMedium value

Certificates earned land on the contact, ready for alumni marketing, referrals and continuing education credit reminders.

Course performance in one reportMedium value

Enrollments, completions and revenue by course sit beside marketing source and pipeline, so leaders see which programs pay off.

Core learner journey

From first click to certificate, on one record.

HubSpot runs the relationship and Canvas runs the learning. The sync module keeps both sides current at each step.

  1. Interest: HubSpot captures the inquiry or Catalog visit and nurtures by course and topic.
  2. Purchase: a Catalog order or a won HubSpot deal enrolls the learner in Canvas.
  3. Learning: enrollment state, progress and activity update the Course Enrollment record and drive nudges.
  4. Completion: the completion and certificate trigger follow-up, upsell and renewal workflows.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the cnv_ prefix in a Canvas property group. Progress and totals are computed in the integration layer so every report agrees.

Internal nameLabelObjectTypeSource / logic
cnv_user_idCanvas User IDContactSingle-line textuser.id; unique
cnv_sis_user_idCanvas SIS User IDContactSingle-line textsis_user_id
cnv_courses_completedCourses CompletedContactNumberCount of completed enrollments
cnv_sis_course_idSIS Course IDCourses objectSingle-line textsis_course_id
cnv_enrollment_idCanvas Enrollment IDCourse EnrollmentSingle-line textenrollment.id; unique
cnv_enrollment_stateEnrollment StateCourse EnrollmentDropdownenrollment_state
cnv_progress_pctProgress %Course EnrollmentNumberrequirement_completed_count ÷ requirement_count
cnv_completed_atCompleted AtCourse EnrollmentDate and timeprogress.completed_at
cnv_last_activity_atLast ActivityCourse EnrollmentDate and timelast_activity_at
cnv_total_activity_minutesTime in Course (min)Course EnrollmentNumbertotal_activity_time ÷ 60
cnv_certificate_earnedCertificate EarnedCourse EnrollmentSingle checkboxCatalog completed certificates
cnv_current_scoreCurrent ScoreCourse EnrollmentNumbergrades.current_score; only if approved
09 — Scope builder

Interactive scope builder

Choose the Canvas data for this engagement and the direction each field syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Canvas × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Canvas HubSpot integration FAQ

Does Canvas integrate with HubSpot?

Yes. Canvas has a publicly documented REST API with OAuth 2.0, a Live Events stream that posts enrollment, progress and completion events as they happen, and Canvas Data 2 for bulk history. Campaign Creators builds a custom integration on these, using a developer key issued by the institution’s Canvas admin.

What data syncs between Canvas and HubSpot?

Learners sync to HubSpot contacts, courses to a course catalog, and enrollments to a Course Enrollment custom object with status, progress, completion and certificate. Where Canvas Catalog is licensed, orders and completed certificates sync too, and a closed deal in HubSpot can enroll a learner in Canvas.

Which system owns which data?

Canvas owns the learning record: enrollment state, progress, completion and scores are official in Canvas, and HubSpot reads them and never edits them. HubSpot owns the relationship, including inquiries, purchases outside Catalog, account ownership and renewals. For credit-bearing students, the institution decides which learner data HubSpot may hold.

What does setting up the Canvas HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and privacy rules, Canvas access (a developer key and a Live Events subscription), identity and ownership rules, the HubSpot data model, the build, backfill, and workflows with a two-week parallel run before launch.

How long does the integration take and what does it cost?

Timeline and cost depend on the Canvas accounts, course types, learner groups and fields in scope (for example whether Canvas Catalog is licensed, the institution’s privacy rules and write-back from HubSpot). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.