Naming Conventions

When creating complex Digital Employees in the Newo.ai platform, it is important to stick to a naming convention to remain consistent and distinguish between different elements. Here are a few best practice naming conventions to adopt:

• Skills: Ensure all Skill identifiers ("Skill Idn") use a CamelCase naming convention with the word "Skill" at the end (e.g., MainSkill, IntroductionSkill, FollowUpSkill, etc.).
• Flows: Ensure all Flow identifiers ("Flow Idn") use a CamelCase naming convention with the word "Flow" at the end (e.g., MainFlow, EmbeddedContextFlow, OutboundCallsFlow, etc.).
• State Fields: Ensure all State Field identifiers ("State Idn") use a snake_case naming convention (e.g., current_skill, next_instruction_step, etc.).
• Parameters: Ensure all Parameter identifiers ("Parameter Idn") use a snake_case naming convention (e.g., current_time, count_value, etc.).
• Events: Ensure all Event identifiers ("Event Idn") use a snake_case naming convention (e.g., user_message, call_ended, call_aborted, etc.).
• Integrations: Ensure all Integration identifiers ("Integration Idn") use a snake_case naming convention (e.g., program_timer, twilio_messenger, etc.).
• Connectors: Ensure all Connector identifiers ("Connector Idn") use a snake_case naming convention (e.g., followup_timer_connector, vapi_connector, magic_sales, etc.).
• Titles: The title of an element can usually be the same as the identifier to avoid confusion.