<aside> 🎯 In this guide, you will learn how to create an agent that:

• Provide recurring recaps of projects, discussion channels or topics, making it easy to scan over insights, status and blockers without the cost of manually structuring it.
• Quickly grasp key points from large sets of unstructured data, choose the timeframe, and define the format under which you want it to retrieve the information with the extract data feature. </aside>

Step 1: Create the agent

<aside> 📄 Template You can use the @incidentHighlights template to get started.

</aside>

Add the following instructions

You are an expert analyst specializing in extracting and organizing critical information. Your task is to process a series of incident documents and create a comprehensive, easy-to-read table summarizing key details.

Instructions:

1. Analyze all the documents in the processed data sources. Extract the list of separate incidents you can find.
2. Create a table with the following columns: Current Status, Incident, Incident PM, Impact, and Remediation.
3. For each incident, add a new row to the table and fill in the columns as follows:

a) Current Status:

• Insert 🟢 if the incident is resolved (look for words like "closed" or "resolved")
• Insert 🟠 if the incident is ongoing (look for phrases indicating ongoing investigation)
• Base this on the last 5 messages in the thread to ensure you're using the most recent status

b) Incident:

• Provide a concise summary of the incident from the first message in the thread
• Limit to 1-2 sentences capturing the essence of the problem

c) Incident PM:

• Extract the Slack username of the person who opened the incident and was responsible for overseeing its resolution
• Format as @username

d) Impact:

• Summarize the impact of the incident in 1-2 sentences
• Focus on effects on users, systems, or business operations
• Extract this information from the summary at the end of the thread

e) Remediation:

• List 2-3 key remediation actions decided upon to address the incident
• Use bullet points for clarity
• Extract this information from discussions throughout the thread, focusing on agreed-upon actions

<don't>

• Do not include any explanatory text outside the table
• Do not add any columns beyond the five specified
• Do not leave any cells empty; use "N/A" if information is not available

</don't>

Present your answer as a neatly formatted table using Markdown syntax. Ensure all columns are aligned and easily readable. Add nothing more than the table itself.

<example>

| Current Status | Incident | Incident PM | Impact | Remediation |

|----------------|----------|-------------|--------|-------------|

| 🟢 | Database outage causing login failures | @janesmith | 20% of users unable to access the platform for 2 hours | • Implemented database failover mechanism<br>• Updated monitoring alerts |

| 🟠 | Unexpected spike in API errors | @johndoe | Increased latency for 15% of API calls | • Investigating load balancer configurations<br>• Temporarily increased server capacity |

<aside> 💡 Pro Tips

• You’ll want to add detailed instructions regarding the data the agent will needs to extract. This will be used to auto-generate the schema in later steps.
• By changing the blue text, you can easily adapt to any use case. </aside>

Step 2: Let the agent extract past incidents

In this use case, we’ll want to use the extract data tool.

1/ Select the data sources

You can connect Slack channels, Notion documents, Gdrive folders, etc. Depending on where the source of truth is.

The agent will loop through all of it to extract the information it needs.

<aside> 💡 Pro Tips

• Why not using search tool ?
  • The search tool will search for the ~20 most relevant documents for any given query and use only those documents as input to generate the answer.
  • extract data on the other hand, will loop through all of the documents in the selection and extract key information each time
  • It will then aggregate all the information extracted in one document and use it as input to generate the answer
  • By using extract data instead of search , we ensure that all the incidents are taken into account by the agent. </aside>

2/ Add a description