> For the complete documentation index, see [llms.txt](https://node-red.gitbook.io/node-red-twitter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node-red.gitbook.io/node-red-twitter/master.md).
# Twitter Analysis using Node-RED
## Introduction
Social media plays a big role in our communication.Tweets are a great source of information however historically it has been difficult for computers to make sense of the unstructured data that contained within a social media feed. But with Watson and AI we can start to make sense of this data.
In this lab we will use Node-RED, a drag and drop low code environment and Watson APIs to do various AI analysis of raw unstructured data to gain useful insight. We will use bunch of services like sentiment analysis, tone analysis, text to speech , and language translator to understand these tweets
## Lab Instructors
Pooja Mistry , IBM Developer Advocate ([@poojamakes](https://twitter.com/poojamakes))
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://node-red.gitbook.io/node-red-twitter/master.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.