Skip to main content
All CollectionsWorkflowsAction Guides
Action: Analyze Industry Trends
Action: Analyze Industry Trends
Updated over a month ago

Overview

The Analyze Industry Trends action enables you to gain valuable insights into the latest developments and patterns in a specific industry relevant to a given company. By providing the company's domain and optionally specifying additional focus areas, you can obtain a comprehensive analysis of the key trends shaping the industry landscape. This action is particularly useful for staying informed about market shifts, emerging technologies, changing consumer preferences, and competitive dynamics that may impact the company's strategy and operations. The output is delivered as a structured JSON object containing the analysis results, which can be seamlessly integrated into subsequent workflow steps for further processing and decision-making.

Usage Examples

  • Outbound Prospecting - By analyzing industry trends for a company’s industry, sales teams can understand the context a prospect’s business may care about.

  • Account Based Marketing - Marketing teams can use trends to inform the messaging and positioning of their product/service for a given customer. This enables better personalization and relevance.

Inputs

  • Company Domain - The URL of the company for which you want to analyze industry trends. This input helps scope the analysis to the specific industry and market context relevant to the company.

  • Additional Research Focus (optional) - Any specific topics, technologies, or areas of interest that you want to emphasize in the industry trend analysis. This input allows you to tailor the research to your particular needs and priorities.

Outputs

The primary output of the Analyze Industry Trends action is a JSON object containing the results of the analysis. The object includes the following key elements:

  • result - A comprehensive summary of the industry trends, covering the most significant developments, patterns, and insights relevant to the company. This narrative provides a high-level overview of the key findings from the analysis.

  • status - An indicator of the success or failure of the action execution. A value of "Success" signifies that the analysis was completed successfully, while "Failed" indicates that an error occurred during the process.

  • statusMessage - A brief message providing additional context about the action status. In case of success, it may simply state "Success," while in case of failure, it may provide more details about the encountered error. This structured output allows you to extract and utilize the industry trend insights in subsequent workflow steps, such as generating reports, informing strategic planning, or triggering specific actions based on the identified opportunities or risks.

Troubleshooting

  • Ensure the company domain is accurate and accessible - If the provided company URL is incorrect or inaccessible, the action may fail to retrieve relevant information for the analysis. Double-check the domain and verify that it points to the company's official website.

  • Provide specific and relevant additional focus areas - While the additional research focus is optional, providing clear and targeted topics can enhance the quality and relevance of the industry trend analysis. Avoid overly broad or generic focus areas that may dilute the insights.

  • Review the output for completeness and coherence - If the generated industry trend summary appears incomplete, disjointed, or lacks key insights, consider refining the inputs or re-running the action. The analysis may benefit from more specific company information or additional focus areas to guide the research effectively.

  • Check for any error messages in the status and statusMessage - In case of a failed execution, pay attention to the status and statusMessage fields in the output. They may provide clues about the nature of the error, such as issues with the company domain, API limitations, or internal processing problems. Use this information to diagnose and resolve the issue before re-running the action.

Did this answer your question?