CampusThreads API documentation for integrations
The CampusThreads Integration API supports approved connections between CampusThreads and external workflow or recruitment systems. Its current public integration surface is intentionally narrower than MCP and is designed around authorized, tenant-scoped integration use cases.
Supported API-oriented workflows
Prospect workflow automation
- Retrieve authorized recent prospect records for an organization.
- Use stable record identifiers for integration deduplication.
- Carry approved recruitment context such as program interest, region, enrollment timing, source, topics, and application status.
- Power polling-based “new prospect” workflows.
Zapier connectivity
- Connect or disconnect the organization’s supported Zapier integration.
- Power the CampusThreads new-prospect trigger.
- Send authorized CampusThreads prospect data into downstream workflows selected by the institution.
Salesforce connectivity
- Start or remove a supported Salesforce connection.
- Retrieve the connected system’s available field catalog for mapping.
- Support organization-controlled prospect synchronization workflows.
Connection validation
- Confirm the authenticated administrator and organization context.
- Read supported integration-connection status.
- Keep integration operations scoped to the administrator’s own organization.
Choose the interface that matches the job
| Need | Recommended interface | Why |
|---|---|---|
| Ask an AI assistant about ambassador operations | CampusThreads MCP | Provides purpose-built tools and contextual descriptions for AI clients. |
| Coordinate shifts, tasks, resources, rewards, assets, or settings through AI | CampusThreads MCP | Covers more than 130 read and action capabilities across the platform. |
| Trigger a workflow when a new prospect appears | Integration API / Zapier | Supports polling and stable record identifiers for workflow automation. |
| Map recruitment data into Salesforce | Native integration | Uses supported connection and field-discovery workflows. |
| Query an internal database directly | Not exposed | CampusThreads provides curated, tenant-scoped capabilities. Raw database access is outside the integration surface. |
What teams can build around CampusThreads
Recruitment follow-up
Route new prospect activity into an approved follow-up workflow while retaining the CampusThreads source and relevant recruitment context.
CRM coordination
Connect ambassador-generated prospect activity to the institution’s CRM workflow without positioning CampusThreads as the enrollment system of record.
Operational reporting
Combine supported CampusThreads records with other approved reporting sources for organization-controlled analysis.
AI-assisted operations
Use MCP when the desired automation involves broader ambassador management, natural-language questions, or actions across multiple CampusThreads workflows.
The full operational surface is available through CampusThreads MCP
Explore ambassadors, recruitment, campaigns, shifts, conversations, tasks, training, visits, community, rewards, assets, invoices, analytics, and settings.
Integration API questions
Is the Integration API the same as CampusThreads MCP?
No. The Integration API supports a focused set of system-to-system workflows. MCP exposes a much broader, AI-friendly catalog of CampusThreads queries and actions.
Does the API provide raw database access?
No. CampusThreads exposes curated integration operations and supported data fields. The integration surface excludes raw database and cross-tenant access.
Can an integration access another organization’s prospects?
No. Supported operations resolve the authenticated administrator’s organization and return data within that tenant context.
Where are production credentials documented?
Credentials are not published on this public capability page. Authorized customers configure supported connections through CampusThreads and approved integration workflows.
Integration request reference
The supported company integration route is POST /api/companies/integration on your configured CampusThreads server. Requests use authenticated CampusThreads account access. The server resolves the organization from that account.
The JSON body identifies a supported integration and operation. The current integration identifiers are salesforce and zapier.
| Operation | Purpose |
|---|---|
connect | Begin the connection flow for the selected integration. |
disconnect | Remove the organization’s connection to that integration. |
fetch | Read the field catalog from a connected Salesforce account for mapping. |
prospects | Retrieve recent prospect records for the authenticated account’s organization. |
For example, an authorized Zapier prospect workflow uses this request body:
{"integrationID":"zapier","operation":"prospects"}Use the connection configured for your organization and keep authentication credentials private. The connect and disconnect operations change connection state. Prospect workflows should send records only to destinations your organization has approved.
Which interface should you use?
Use the Integration API for the system-to-system workflows described above. For assistant-driven work across shifts and other program records, use the MCP server and tool reference.
API and MCP access are included with the AI colleague under fair-use limits. See pricing and access or the free nonprofit offer.