This Langflow flow creates a two-stage content creation system for the hospitality industry. The flow begins with a Chat Input component that captures user messages and feeds them to a Planner Agent. This first agent uses a specialized prompt to act as a content briefing specialist, systematically gathering information from users about their content needs through a structured questionnaire covering content type, target channel, property details, audience, key features, tone, keywords, length requirements, and additional instructions.

The flow includes a conditional routing system that checks whether the Planner Agent has completed its briefing process. An If-Else component examines the agent's response to determine if it starts with "=== FINAL BRIEFING ===" which signals completion of the information gathering phase. If this condition is met, the message is routed to the Copywriter Agent for content creation. If the briefing is not yet complete, the system continues the conversation with the user to gather more information.

The Copywriter Agent receives completed briefings and transforms them into polished content pieces. This agent has access to a URL tool that allows it to fetch additional information from web pages to enrich the content with relevant data about locations, attractions, or other hospitality-related details. The final content is then displayed through a Chat Output component, creating a complete workflow that takes users from initial content requests through structured briefing to final deliverable content optimized for hospitality businesses.

The flow can be extended using additional Langflow components to create a more comprehensive content management system. You could integrate Vector Store components to build a knowledge base of successful content examples, add API Request components to automatically publish content to various platforms, or incorporate Message History to maintain context across multiple content creation sessions. The system could also be enhanced with Webhook components to trigger content creation from external systems like booking platforms or content calendars, and Redis memory could store brand guidelines and style preferences for consistent content generation across different team members.