Files
dify/app1_email_generator.yml

168 lines
6.0 KiB
YAML

app:
description: 'documentation and source can be found under the following link: https://drive.google.com/drive/folders/13IXNtJGFKZnBelD2caNwWF8qo8LAVnos?usp=sharing'
icon: 🤖
icon_background: '#FFEAD5'
mode: completion
name: day1
use_icon_as_answer_icon: false
dependencies:
- current_identifier: null
type: marketplace
value:
marketplace_plugin_unique_identifier: langgenius/openai:0.2.6@e2665624a156f52160927bceac9e169bd7e5ae6b936ae82575e14c90af390e6e
version: null
kind: app
model_config:
agent_mode:
enabled: false
max_iteration: 10
strategy: react
tools: []
annotation_reply:
enabled: false
chat_prompt_config: {}
completion_prompt_config: {}
dataset_configs:
datasets:
datasets: []
retrieval_model: multiple
top_k: 4
dataset_query_variable: ''
external_data_tools: []
file_upload:
allowed_file_extensions:
- .JPG
- .JPEG
- .PNG
- .GIF
- .WEBP
- .SVG
- .MP4
- .MOV
- .MPEG
- .WEBM
allowed_file_types: []
allowed_file_upload_methods:
- remote_url
- local_file
enabled: false
image:
detail: high
enabled: false
number_limits: 3
transfer_methods:
- remote_url
- local_file
number_limits: 3
model:
completion_params:
max_tokens: 1000
stop: []
temperature: 0.7
mode: chat
name: gpt-4
provider: langgenius/openai/openai
more_like_this:
enabled: false
opening_statement: null
pre_prompt: "{{ \nYou are a professional email marketing specialist and cultural\
\ communication expert. Your task is to generate culturally appropriate thank\
\ you emails that match the specified tone and language.\n\n## Input Variables:\n\
- {{recipient_name}}: The name of the email recipient. (Assumed to be an input,\
\ though not visible in the screenshot).\n- {{reason_for_thanks}}: The primary\
\ reason for the email (e.g., \"kick-off meeting\").\n- {{tone}}: The desired\
\ tone of the email (e.g., \"casual\").\n- {{language}}: The desired language\
\ (e.g., \"english\").\n- {{additionalDetails}}: Specific extra context to include\
\ (e.g., \"meeting was in 'bear' pub\").\n- {{sender_name}}: The name of the sender\
\ (e.g., \"Plotrek\").\n- {{include_upsell}}: A boolean (`true` or `false`) indicating\
\ if a business opportunity suggestion should be included.\n\n## Core Requirements:\n\
1. Generate personalized thank you emails based on the provided inputs\n2. Adapt\
\ tone and style to match the specified preference\n3. Ensure cultural appropriateness\
\ for the target language\n4. Include proper email structure and formatting\n\
5. If upsell is requested, integrate it naturally without being pushy\n\n## Language\
\ Guidelines:\n\n### English Emails:\n- Use appropriate salutations (Dear, Hi,\
\ Hello based on formality)\n- Maintain professional email structure\n- Include\
\ clear subject lines\n- Use proper closing (Best regards, Sincerely, Warmly,\
\ etc.)\n\n### Japanese Emails:\n- Use proper Japanese email structure:\n - Start\
\ with appropriate greeting (拝啓 for formal, こんにちは for casual)\n - Include seasonal\
\ context when appropriate\n - Use proper honorifics (様 for formal, さん for casual)\n\
\ - End with appropriate closing (敬具 for formal, よろしくお願いします for casual)\n- Consider\
\ cultural nuances in expression\n\n## Tone Adaptations:\n- **Formal**: Professional\
\ language, proper titles, structured format\n- **Casual**: Friendly language,\
\ first names, relaxed structure\n- **Enthusiastic**: Exclamations, positive adjectives,\
\ energetic tone\n- **Sincere**: Emotional depth, personal touches, heartfelt\
\ language\n\n\n## Output Format:\nReturn a JSON object with the following structure:\n\
{\n \"subject\": \"Email subject line\",\n \"body\": \"Complete email body with\
\ proper formatting\",\n \"tone_analysis\": \"Brief description of how the tone\
\ was implemented\",\n \"cultural_notes\": \"Any cultural considerations applied\"\
\n}\n\n\n## Special Instructions:\n- Always personalize the content based on the\
\ specific reason for thanks\n- Keep emails concise yet meaningful (150-300 words\
\ typically)\n- For upsell requests, suggest relevant opportunities naturally\n\
- Ensure all contact information and names are used correctly\n- Adapt formality\
\ levels based on the relationship context\n\n}}"
prompt_type: simple
retriever_resource:
enabled: true
sensitive_word_avoidance:
configs: []
enabled: false
type: ''
speech_to_text:
enabled: false
suggested_questions: []
suggested_questions_after_answer:
enabled: false
text_to_speech:
enabled: false
language: ''
voice: ''
user_input_form:
- text-input:
default: ''
label: Recipient Name
max_length: 48
required: true
variable: recipient_name
- paragraph:
default: ''
label: Reason for Thanks
max_length: 200
required: true
variable: reason_for_thanks
- select:
default: '`formal` - Professional and formal'
label: Email Tone
options:
- '`formal` - Professional and formal'
- '`casual` - Friendly and relaxed'
- '`enthusiastic` - Warm and expressive'
- '`sincere` - Heartfelt and genuine'
required: true
variable: tone
- select:
default: '`english` - English'
label: Language
options:
- '`english` - English'
- '`japanese` - 日本語'
required: true
variable: language
- text-input:
default: ''
label: additionalDetails
max_length: 100
required: false
variable: additionalDetails
- text-input:
default: ''
label: Your Name
max_length: 48
required: true
variable: sender_name
- checkbox:
default: ''
label: Include business opportunity suggestion
required: false
variable: include_upsell
version: 0.4.0