What this category's data looks like
In the enrollment consultation conversion scenario for training institutions, materials are mainly of three types: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures provide the course name, class type, start date, and fee basis; consultation records carry the student's name, contact information, intended course, and communication time; trial class schedules record the trial time, campus, instructor, and receipt signature. The three types of materials come from different sources: brochures are published by marketing or academic affairs, consultation records are entered one by one by enrollment consultants, and trial schedules are generated by academic affairs scheduling. In terms of update cadence, brochures change with class terms, consultation records are appended with each communication, and trial schedules are arranged weekly. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. The same student's intended course may be written differently in two materials, class term dates and trial dates may be misaligned, and receipts may lack signatures. When entering this feature, brochures and trial schedules serve as external system-side data, consultation records serve as intake input, and the HTTP interface retrieves them as agreed; missing items are completed in the follow-up questioning step.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The intake records and the completed question items are parsed from the response by subsequent nodes, or handled by the external system as agreed to finish the process. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Enrollment brochure | Whether the course name, class type, start date, and fee basis are consistent between the brochure and the consultation record | Take the brochure fields and compare them item by item with the consultation record; mark items as missing first if dates and quantities do not match |
| Consultation record | Whether the student's name, intended course, and communication time are complete, and whether a consultant signature or receipt is present | Check against the field checklist; if contact information or intended course is missing, enter follow-up questioning; record a missing signature separately |
| Trial class schedule | Whether the trial time, campus, instructor, and brochure class term are synchronized, and whether the version is the latest | Check the scheduling version against the brochure version; list date misalignments or unsynchronized versions as items pending follow-up questioning |
| HTTP request configuration | Whether the placeholder variables in the request address, request headers, and request body can be resolved into actual values | View the fully rendered address in the request preview, check the request header names and value sources, compare the response with a sample request, and confirm that Authorization, variables, responseData are consistent with the interface agreement |
Three common errors
- Symptom: the external system receives empty fields. Cause: request body placeholder variables are unresolved, the output names of preceding nodes are inconsistent with the interface agreement, and the field names do not match.
- Symptom: the request returns 401. Cause: the request header authentication information is not passed in as required by the external system, the
Authorizationvalue source is wrong, or it is not switched with the environment. - Symptom: the same student's intended course and class term dates do not match between the two materials. Cause: the brochure version is not synchronized, the consultation record still uses the old class term, and the trial class schedule lacks a receipt signature.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the values of variables and responseData are consistent with the interface agreement, and when the status code is 200, forward it to the person in charge for handling.
Business test: submit a question that lacks key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder, confirm it comes from a global variable, system variable, or the output of a preceding node, and view the fully rendered address in the request preview.
- Use a sample request to compare the returned fields, check the request header names and value sources, and after confirming that
Authorizationis consistent with the interface agreement, forward it to the person in charge for handling.