Campus Cloud Integration
The Campus Cloud integration pushes deal and person data from Pipedrive to the Campus Cloud Student Information System (SIS). It is triggered manually from the deal sidebar panel and is designed for enrollment workflows where admissions staff need to send accepted student data to the SIS.
Configuration
Enable the integration in the Formidable Forms settings pane (which also houses Campus Cloud settings) and provide the following credentials:
| Setting | Description |
|---|---|
| Base Endpoint | The root URL of the Campus Cloud API (e.g., https://api.campuscloud.com/v1). |
| UserName | API username for authentication. |
| TokenID | API token ID for authentication. |
All API calls use these credentials, sent as URL-encoded form parameters alongside each request.
Field Mapping
The enrollment mapping (ccsEnrollmentMap) defines how Pipedrive fields translate to Campus Cloud fields. It is organized into five sections:
Person Fields (person)
Maps Pipedrive person field names to Campus Cloud lead fields.
| Pipedrive Field | Mapping Property | Description |
|---|---|---|
| Standard fields (e.g., Email, Phone) | ccsField |
The CCS field name to populate. |
| Phone | ccsFields (array) |
Phone can map to multiple CCS fields (e.g., both Phone and MobilePhone). |
| Custom person fields | ccsField |
Resolved by Pipedrive field name; enum values are converted from option IDs to labels. |
Deal Fields (deal)
Maps Pipedrive deal field names to Campus Cloud lead fields. Works identically to person fields: enum option IDs are resolved to labels before sending.
Application Fields (application)
Maps Pipedrive deal field names to Campus Cloud application fields by numeric field ID.
{
"Program of Interest": {
"ccsFieldId": "42"
}
}
These are posted via the PostApplicationFields endpoint after the lead is created or updated.
Custom Fields (custom)
Maps Pipedrive deal field names to Campus Cloud custom fields by numeric field ID. Posted via the PostCustomFields endpoint.
{
"Referral Source": {
"ccsFieldId": "15"
}
}
Enum Value Overrides (enumValueMap)
A top-level map that translates Pipedrive enum labels to Campus Cloud values before sending. Keyed by Pipedrive field name, with a nested object mapping label to label.
{
"Ethnicity": {
"Hispanic": "Hispanic or Latino",
"Two or more races": "Two or More"
}
}
This applies across all mapping sections (person, deal, application, custom).
Static Values (static)
Key-value pairs sent with every push, regardless of deal data. Useful for fixed values like enrollment term or campus code.
{
"Fall 2026": "EnrollmentTerm",
"MAIN": "CampusCode"
}
The Campus Cloud integration requires that the Pipedrive person and deal field caches (pdPersonFieldsCache, pdDealFieldsCache) are populated. These caches are created automatically during Formidable webhook processing or when the settings page loads field data. If the caches are empty, enum fields will not resolve correctly.