Extend predefined-reply sources with the openai_fine_tuning_predefined_replies filter
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Adjust the predefined-reply training array through the supported hook.
Where to goDevelopment integration → hook openai_fine_tuning_predefined_replies
Before you start
- Use an account with Developer and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide helps you do
Adjust the predefined-reply training array through the supported hook. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Development integration → hook openai_fine_tuning_predefined_replies.
- Select the exact record or option described in this guide.
- Complete the displayed fields or action using the rules below.
- Save or submit once and resolve any validation response.
- Check the resulting record, status, file, notification or integration effect.
Fields and options
ActionExtend predefined-reply sources with the openai_fine_tuning_predefined_replies filter
Exact navigationDevelopment integration → hook openai_fine_tuning_predefined_replies
Module version1.0.0
VerificationVerify the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.
Rules and limits
- Return records in the structure expected by Fine_tuner.
- Avoid duplicate, contradictory or sensitive examples.
Check it worked
- The supported extend predefined-reply sources with the openai_fine_tuning_predefined_replies filter flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Restrict the API key and AI settings to authorised administrators.
- Do not submit confidential, special-category or unnecessary personal data to the external AI provider.
- Check generated text before using it in customer, staff, legal, financial or compliance communication.
- Monitor provider billing and retention independently because this module has no built-in cost dashboard.
Related guides
Was this guide useful?Your response is stored only in this browser.
