Integration

Weworkbook integration

Weworkbook is a CRM, learning and student management system for training organisations (RTOs, CRICOS institutes, short course providers). List and search students, read a student's details, enrolments, unit outcomes, notes and schedules, create and update students, enrol a student in a course schedule, enrol units and set unit outcomes, add student notes, list courses, course units, users, note categories and outcomes, and manage webhooks. The API has no delete route. Authentication is OAuth2: create an app under your profile name, API Settings, in Weworkbook to get a client id and secret.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Weworkbook.Built from the 21 Weworkbook tools below, on the connection you add once.

What you can do with Weworkbook

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Student, 4 operations

  • create_studentCreate studentPOSTCreate a student record from a first name, a last name and one contact (contact type plus value). Returns the new studentId. AVETMISS fields are only stored when the organisation requires AVETMISS reporting.
  • get_studentGet studentGETRead one student's personal record: names, USI, date of birth, gender, phone numbers, emails, residential and postal address. Returns personal data.
  • list_studentsList studentsGETList students one page at a time (count per page, up to 1000), searchable by name or email and filterable to active students. Students are in resource; meta.lastPage and meta.total give the paging. Returns personal data.
  • update_studentUpdate studentPUTUpdate a student's personal information. The vendor does not say whether fields left out are kept: read get_student first and send back what must not change. AVETMISS fields only apply when AVETMISS is required.

Webhook, 3 operations

  • create_webhookCreate webhookPOSTSubscribe a URL to one webhook type (typeId from list_webhook_types) for Add, Edit, Delete or Automate actions; deliveries are HTTP POST. No signing secret is documented, so deliveries cannot be verified.
  • list_webhooksList webhooksGETList the webhook subscriptions of the account: id, event type, target url, enabled flag and actions (Add, Edit, Delete).
  • update_webhookUpdate webhookPUTChange a webhook's url, actions or enabled flag (there is no delete route: send enabled=0 to stop deliveries). The vendor does not say whether fields left out are kept; read list_webhooks first.

Course, 2 operations

  • list_coursesList coursesGETList the courses of the organisation (courseId, courseCode, courseName). Pass a courseId to list_course_units or list_schedules.
  • list_course_unitsList course unitsGETList the units (modules) of one course: unitIdentifier, unit type (C core, E elective) and unit name. Pass a unitIdentifier to enrol_unit.

Enrolment, 2 operations

  • create_enrolmentCreate enrolmentPOSTEnrol a student in a course schedule (scheduleId from list_schedules) with a payment status and trainee flag. Returns the new enrolmentId; add units with enrol_unit.
  • list_student_enrolmentsList student enrolmentsGETList a student's current enrolments: course, delivery method, dates, qualification status and every enrolled unit with its outcome and enrolmentModuleId (for update_enrolment_outcome).

Note, 2 operations

  • create_student_noteCreate student notePOSTAdd a note to a student's record, written as a Weworkbook user (creatorId from list_users), optionally with a follow-up date, follow-up user and note category.
  • list_student_notesList student notesGETList the notes on a student's record: text, author, creation date, follow-up date and user, category, and whether it came from the student learning portal or the system.

Schedule, 2 operations

  • list_schedulesList schedulesGETList course schedules (scheduleId, city, start and end date), optionally for one course. Pass a scheduleId to create_enrolment.
  • list_student_schedulesList student schedulesGETList course schedules for one student (scheduleId, city, start and end date), optionally for one course. The vendor reference does not say how this list differs from list_schedules.

Enrollunit, 1 operation

  • enrol_unitEnrol unitPOSTEnrol one course unit into an existing student enrolment. enrolmentId comes from list_student_enrolments or create_enrolment; unitIdentifier from list_course_units for that course.

Module, 1 operation

  • update_enrolment_outcomeUpdate enrolment outcomePUTSet the outcome of one enrolled unit, or of every Core or Elective unit at once with bulkUpdate=1 and unitType. Bulk only changes units whose outcome is 'Continuing enrolment' or 'Not yet started'.

Notecategory, 1 operation

  • list_note_categoriesList note categoriesGETList the student note categories (categoryId, categoryName). Pass a categoryId as noteCategoryId to create_student_note.

Outcome, 1 operation

  • list_outcomesList outcomesGETList the unit outcomes the organisation can set (outcomeId, description, Western Australia state outcome id). Pass an outcomeId to update_enrolment_outcome.

User, 1 operation

  • list_usersList usersGETList the users of the connected Weworkbook company (userId, first and last name, whether registration is confirmed), optionally filtered by name. A userId is the creatorId of create_student_note.

Webhook type, 1 operation

  • list_webhook_typesList webhook typesGETList the webhook event types (id, name such as Student Notes). Pass an id as typeId to create_webhook.

Use Weworkbook from Claude Code, Cursor or Codex

Connect Weworkbook in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Weworkbook operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Weworkbook

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Weworkbook once

    Add your Weworkbook connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Weworkbook integration FAQ

What can you do with the Weworkbook integration?

LiveContext exposes 21 operations on Weworkbook, covering student, webhook, course and enrolment.

Popular integrations

Browse the whole catalog