Course Catalog Creation with AI Tools

Scenario

A Salesforce admin at your institution wants to build a complete course catalog from department spreadsheets and PDFs before scheduling and enrollment work begins. To avoid creating course records and linking courses manually, the admin connects a coding agent to the Headless 360 MCP Server (Beta) and provides the department files. The agent analyzes the courses, identifies missing fields, and proposes the catalog structure for review. After the admin approves, the agent creates the course records and links each course to its offering department.

Note Headless 360 MCP Server is a beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this beta service is at the Customer's sole discretion. For more information, see Headless 360 MCP Server (Beta).

Requirements

• Education Cloud Full Access permission set. The agent checks for and assigns the required permission sets based on your privileges, so it never grants access that you don't have.
• A coding agent, such as Agentforce Vibes or Claude Code, connected to the Headless 360 MCP Server (Beta) with access to Education Cloud setup skills. For Agentforce Vibes, no installation is required. Agentforce Vibes installs, enables, and updates AI Skills automatically. You can manage them from the Skills page, under Toolkit, in Agentforce Vibes. For Claude Code, install the Salesforce Development plugin, which provides Salesforce-specific skills and org context through hosted Model Context Protocol (MCP) servers.

Suggested Technology and Experience

Recommended for Salesforce admins who are comfortable with Setup and with running a coding agent against a connected org. No prior experience with a specific skill is required.

Related Documentation

• Model Courses and Curricula
• Salesforce Hosted MCP Servers
• Salesforce Development Plugin
• Get Started with Agentforce Vibes

Agentic Tips

• Describe your goal in your own words. For example:
  • "Import our course catalog from this spreadsheet."
  • "Here's our catalog PDF. Create the courses for the College of Engineering."
  • "Set up our courses, and link the labs to their lectures."
• Provide reliable sources. A structured spreadsheet or CSV file is more reliable than a web page, which can return incomplete results. Include course codes, names, and credit hours so that the agent creates complete records.
• Specify the course-offering account. Courses link to the business account for the college or department that provides them. Be ready to provide that account before you start.
• Decide how to handle lecture and lab pairs. When the agent finds lecture and lab pairs, it asks whether to create them as separate courses or as linked courses that students take together. State your preference before the agent creates records.
• Review the data quality report. The agent reports missing fields and asks for additional sources or your approval before creating records with placeholder values. It doesn't invent missing data.
• Avoid pasting credentials into a prompt. The agent acts as your authenticated user through the connected org.

Design Considerations

• The agent creates course records only. It creates course records in bulk and links them to their provider account. It doesn't create learning programs, prerequisites, course offerings, sections, or enrollment. Set those up separately.
• The agent evaluates data before committing. It reports which fields are complete and which are missing, pauses on lecture and lab pairs, and identifies existing courses so that you update, skip, or review them.
• Multiple formats that use the same code aren't duplicates. When one course code appears with different credit hours or delivery formats, the agent treats them as variants and asks how to represent them rather than merging them.
• Confirm record visibility after import. After the agent builds the catalog, check that the running user's profile can see the created records. If needed, set field-level and record-type access in Setup.