mirror of
https://github.com/labring/FastGPT.git
synced 2026-05-05 01:02:59 +08:00
Archer
4b24472106
* docs(i18n): translate batch 1 * docs(i18n): translate batch 2 * docs(i18n): translate batch 3 (20 files) - openapi/: app, share - faq/: all 8 files - use-cases/: index, external-integration (5 files), app-cases (4 files) Translated using North American style with natural, concise language. Preserved MDX syntax, code blocks, images, and component imports. * docs(i18n): translate protocol docs * docs(i18n): translate introduction docs (part 1) * docs(i18n): translate use-cases docs * docs(i18n): translate introduction docs (part 2 - batch 1) * docs(i18n): translate final 9 files * fix(i18n): fix YAML and MDX syntax errors in translated files - Add quotes to description with colon in submit_application_template.en.mdx - Remove duplicate Chinese content in translate-subtitle-using-gpt.en.mdx - Fix unclosed details tag issue * docs(i18n): translate all meta.json navigation files * fix(i18n): translate Chinese separators in meta.en.json files * translate * translate * i18n --------- Co-authored-by: archer <archer@archerdeMac-mini.local> Co-authored-by: archer <545436317@qq.com>
19 lines
497 B
Plaintext
19 lines
497 B
Plaintext
---
|
|
title: Specified Reply
|
|
description: FastGPT Specified Reply module overview
|
|
---
|
|
|
|
## Features
|
|
|
|
- Can be added multiple times (helps keep complex workflows visually clean by avoiding tangled connections)
|
|
- Supports manual input
|
|
- Supports external input
|
|
- Outputs results to the client
|
|
|
|
The Specified Reply module is typically used for special-case responses. There are two ways to define reply content:
|
|
|
|
1. Manually enter fixed content.
|
|
2. Use variable references.
|
|
|
|
|