Generate Images from Text with IBM Granite Vision 3.3 2B AI Model

Generate Images from Text with IBM Granite Vision 3.3 2B AI Model

🌍 Overview

This workflow uses the ibm-granite/granite-vision-3.3-2b model (hosted on Replicate) to generate AI images. It starts manually, sends a request to the Replicate API, waits for the result, and finally outputs the generated image link.

Think of it as your AI art assistant β€” you click once, and it handles the full request/response cycle for image generation.

🟒 Section 1: Trigger & API Setup

πŸ”— Nodes:

Manual Trigger* β†’ Starts when you click Execute. Set API Key* β†’ Stores your Replicate API Key safely in the workflow.

πŸ’‘ Beginner takeaway: This section is like turning the key in the ignition. You start the workflow, and it loads your credentials so you can talk to Replicate’s API.

πŸ“ˆ Advantage: Keeps your API key stored inside the workflow instead of hard-coding it everywhere.

🟦 Section 2: Create Prediction

πŸ”— Nodes:

HTTP Request (Create Prediction)** β†’ Sends a request to Replicate with the chosen model (granite-vision-3.3-2b) and input parameters (seed, temperature, max_tokens, etc.).

πŸ’‘ Beginner takeaway: This is where the workflow actually asks the AI model to generate an image.

πŸ“ˆ Advantage: You can tweak parameters like creativity (temperature) or randomness (seed) to control results.

🟣 Section 3: Polling & Status Check

πŸ”— Nodes:

Extract Prediction ID (Code)** β†’ Saves the unique job ID. Wait (2s)** β†’ Pauses before checking status. Check Prediction Status (HTTP Request)** β†’ Calls Replicate to see if the image is ready. If Condition (Check If Complete)** β†’

βœ… If status = succeeded β†’ move to result πŸ”„ Else β†’ go back to Wait and check again

πŸ’‘ Beginner takeaway: Since image generation takes a few seconds, this section keeps asking the AI β€œare you done yet?” until the image is ready.

πŸ“ˆ Advantage: No need to guess β€” the workflow waits automatically and retries until success.

πŸ”΅ Section 4: Process Result

πŸ”— Nodes:

Process Result (Code)** β†’ Extracts the final data:

βœ… Status βœ… Output image URL βœ… Metrics (time taken, etc.) βœ… Model info

πŸ’‘ Beginner takeaway: This section collects the finished image link and prepares it neatly for you.

πŸ“ˆ Advantage: You get structured output that you can save, display, or use in another workflow (like auto-sending images to Slack or saving to Google Drive).

πŸ“Š Final Overview Table

| Section | Nodes | Purpose | Benefit | | -------------------- | ---------------------------------- | --------------------------- | --------------------------- | | 🟒 Trigger & Setup | Manual Trigger, Set API Key | Start + load credentials | Secure API key management | | 🟦 Create Prediction | HTTP Request | Ask AI to generate image | Control creativity & output | | 🟣 Polling | Extract ID, Wait, Check Status, If | Repeatedly check job status | Auto-wait until done | | πŸ”΅ Process Result | Process Result | Extract image + details | Get clean output for reuse |

πŸš€ Why This Workflow is Useful

Automates full API cycle** β†’ From request to final image URL Handles delays automatically** β†’ Keeps checking until your image is ready Customizable parameters** β†’ Adjust creativity, randomness, and token limits Reusable** β†’ Connect it to email, Slack, Notion, or storage for instant sharing Beginner-friendly* β†’ Just plug in your API key and hit *Execute

0
Downloads
290
Views
7.53
Quality Score
beginner
Complexity
Author:Yaron Been(View Original β†’)
Created:8/13/2025
Updated:11/17/2025

πŸ”’ Please log in to import templates to n8n and favorite templates

Workflow Visualization

Loading...

Preparing workflow renderer

Comments (0)

Login to post comments