What this category's data looks like
This category's data covers three types of materials: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures specify the course name, number of class hours, start date, and refund terms; consultation records log the parent's contact information, intended course, communication date, and consultant signature; trial class schedules state the trial time, instructor, classroom number, and parent acknowledgment. The field characteristic is that the name, quantity, and date of the same record must be consistent across the brochure, consultation record, and trial schedule, and signatures and acknowledgments must not be missing. When materials enter this function, the enrollment brochure provides the externally visible basis for the course and authorization scope, while consultation records and trial class schedules serve as internal bases visible to restricted identities, and the HTTP node carries the corresponding fields when requesting from external systems. The update cadence changes with enrollment batches and trial scheduling, and each change requires synchronizing the version and completing the signature or acknowledgment.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "externally available entry point and authorization scope" is completed by subsequent nodes parsing the response, or by the external system handling it as agreed. The request URL, path parameters, request headers, and placeholder variables in the request body come from global variables, system variables, or upstream node outputs, and the rendered result can be checked in the request preview.
| Object | Check | Verification action |
|---|---|---|
| Enrollment brochure | The course name, number of class hours, start date, and refund terms must match the consultation record and trial class schedule item by item, with complete signatures or acknowledgments | In the request preview, view the rendered full URL and request body fields, and check whether the brochure fields are consistent with the external interface agreement |
| Consultation record | The parent's contact information, intended course, communication date, and consultant signature must match the brochure and trial schedule, with synchronized versions | Check the request header names and value sources, confirm that authentication information is passed in as required by the external system, and inspect the origin of each placeholder in the variables panel |
| Trial class schedule | The trial time, instructor, classroom number, and parent acknowledgment must be consistent with the brochure and consultation record; if a signature or acknowledgment is missing, it must not be exposed externally | Use a sample request to compare the response, and check whether the responseData fields match the trial class schedule record |
| Request headers and variable sources | Authentication information is passed in as required by the external system, and each placeholder can be traced to a global variable, system variable, or upstream node output | In the variables panel, check the sources of Authorization and variables, and confirm that placeholders resolve to actual values |
Three common errors
- Symptom: The number of class hours and start date for the same course do not match between the enrollment brochure and the consultation record. Cause: The two materials are maintained separately, versions are not synchronized, and updates are not unified after changes.
- Symptom: The trial class schedule lacks a parent acknowledgment or consultant signature, yet the external entry point is still accessible. Cause: Materials are incompletely collected, and the authorization scope is not tightened according to signature and acknowledgment status.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information is not passed in as required by the external system, or the request body fields are inconsistent with the interface agreement.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that responseData matches the sample.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the variables panel, check the source of each placeholder, and confirm that the value origins of
Authorization,variables, andresponseDataare traceable. - Use a sample request to compare the response, and check whether the names, quantities, dates, and signatures/acknowledgments of the enrollment brochure, consultation record, and trial class schedule are consistent.