What the data for this category looks like
Data for new employee onboarding guidance is primarily sourced from enterprise HR system onboarding records, official employee handbooks, department workstation guidance documents, and IT equipment checkout flow sheets. Data is synchronized in batches 1 to 3 days before onboarding. Real-time updates occur on the day of onboarding for temporary changes such as assigned contact person adjustments or workstation changes. Document structure centers on process nodes, and includes modules such as check-in, equipment pickup, department liaison, and account activation. Fields include employee ID, department name, hire date, assigned contact person phone number, workstation number, and others. Phone numbers use an 11-digit numeric format. Workstation numbers use a combination of letters and numbers. Hire dates follow the YYYY-MM-DD standard format. Reference only; verify against the target FastGPT release and deployment documentation.
Constraints imposed by these characteristics on the tool calling and plugins workflow
HR system data sources require tool calling to integrate with enterprise internal open APIs, and valid identity verification parameters must be configured. The mixed batch and temporary update rhythm requires tool calling to support on-demand cache refresh, to avoid use of expired employee information. The multi-node process structure requires tool calling to automatically match corresponding plugins based on the current guidance node. For example, the equipment management plugin is called during the equipment pickup phase, and the contact directory plugin is called during the department liaison phase. Dynamic employee-specific fields require tool call input parameters to bind unique identifiers such as employee ID, to ensure returned information matches the current onboarding new employee.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | Set to auto | Allows the model to automatically select the appropriate tool based on the onboarding guidance process nodes, adapting to multi-step onboarding scenarios |
functionCall | Enable forced function call mode | Ensures tool call return results meet the structured output requirements of onboarding guidance, avoiding unexpected natural language responses |
| Tool call timeout duration | 30-60 seconds | Adapts to the standard interface response times of HR systems and equipment management systems, preventing timeout interruptions of onboarding processes |
| Plugin authorization configuration | Bind official keys for HR system, equipment management, and contact directory plugins | Ensures tool calling can legally access exclusive data from corresponding systems |
| Tool trigger rules | Dynamically bind input parameters using employee ID | Ensures each new employee’s onboarding process calls tool data specific to their individual profile |
Three common mistakes
- Phenomenon: Tool calling returns an error stating the model does not support function calls, with a status code of 400. Cause: The
functionCallparameter is not configured correctly, and a model version that does not support tool calling is used. - Phenomenon: Third-party browsers display cross-origin block prompts when calling FastGPT interfaces. Cause: Cross-origin whitelists for corresponding business domain names are not added to the FastGPT gateway configuration.
- Phenomenon: Searching the onboarding knowledge base returns no matching results, with the interface prompting "No relevant documents found". Cause: Onboarding-related documents such as employee handbooks and workstation guidance are not correctly associated with the corresponding knowledge base categories.
How to confirm the configuration is complete
- Trigger a simulated new employee onboarding process, and check whether the corresponding node tools are automatically called and expected structured information is returned.
- View tool calling logs, confirm that the
toolChoiceparameter is active, and the model has automatically selected the tool matching the current process node. - Submit a cross-origin test request, and confirm that no cross-origin block error is received on the browser side.
- Temporarily adjust the workstation information of a test employee, and check whether updated workstation data can be retrieved after tool calling.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.