GROQ LLAVA V1.5 7B
Configured with Extract From File, HTTP Request, Telegram, Telegram Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Messaging
- Transform
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Telegram send the text | Messaging | Telegram | See node parameters |
| Get only the text | Transform | Edit Fields | See node parameters |
| HTTP Request GROQ LLAVA | Web / API | HTTP Request | POST |
| convert the image file to base64 | Transform | Extract From File | binaryToPropery |
| Receive the File | Messaging | Telegram | file |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
telegramApi
Workflow notes
Set Up
Set Up
Open the Telegram app and search for the BotFather user (@BotFather) Start a chat with the BotFather Type /newbot to create a new bot Follow the prompts to name your bot and get a unique API token Save your access token and username
Start Using
Once you set the Bot, you can send the image. The second node get the image and send to the next node to be convert in base64, that is required by Groq in the documentation.
Using GROQ API
Using GROQ API
Now we send the image in base64 to the API and get the description of the image.
GROQ LLAVA V1.5 7B
GROQ LLAVA V1.5 7B
Purpose and structure
This folder contains the GROQ LLAVA V1.5 7B workflow. Its executable nodes use extractFromFile, httpRequest, set, telegram, telegramTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Telegram Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1800_HTTP_Telegram_Automation_Webhook.json MIT; preserve source notices.