n8n Edit Image text alignment over a Sume-generated image
n8n 2.39 adds horizontal and vertical alignment to Edit Image's Add Image Text. Generate the picture with Sume, then place the exact words on it.

Generate the image with Sume first, then let n8n's Edit Image node write the words on it. Its Add Image Text operation now has horizontal and vertical alignment options, so you can center a caption without hand-tuning X and Y. Sume supplies the picture; n8n places the text.
The alignment change is from the n8n release notes, read 2026-09-30. The job and result behavior is from Sume's Jobs and results page.
What did n8n 2.39 change?
n8n 2.39 (2026-09-08) says the Edit Image node's Add Image Text operation now includes Horizontal Alignment (Left, Center, Right) and Vertical Alignment (Top, Middle, Bottom), letting you position text without manual trial and error on Position X/Y.
How do the two steps connect?
Submit the Sume request in async mode. The response carries request_id (the job id), status_url and result_url. Results are available only after completion, so poll status_url until the job is terminal before asking for the result. A completed job lists artifacts, each with a url on media.sume.com; use those Sume media URLs, not raw provider URLs. Download that URL into the workflow (my suggestion: an HTTP Request node returning a file), then pass the binary to Edit Image.
| Step | Node | What it does |
|---|---|---|
| 1 | HTTP Request | Submit the image job to Sume; keep request_id |
| 2 | Wait / poll | Read status_url until terminal |
| 3 | HTTP Request | Fetch the artifact url from the result |
| 4 | Edit Image | Add Image Text with Center / Middle alignment (n8n 2.39) |
Why overlay text instead of prompting for it?
When the words must be exact, a title, a price or a legal line, writing them in your workflow keeps them under your control and lets you change them without regenerating the picture. That is a design choice, not a Sume or n8n claim. Prompt for an image with clear empty space where the text will sit.
What about the wait?
Do not hold one HTTP node open for a slow job; poll instead, as covered in n8n Wait node and next_poll_after_seconds. For the basic generation setup see n8n AI image generation.
Sources
Related posts
More in Integrations
- n8n MCP workflow access error vs a Sume insufficient_scope
n8n now links MCP workflow access errors to workflow settings. A Sume failure reads differently: insufficient_scope means the OAuth session lacks mcp:write.
- n8n nested AI agent tool: one idempotency_key per Sume generation
n8n's AI Agent Tool can now use its own tools under a pre-v3 parent agent. If both levels reach a Sume paid tool, reuse one idempotency_key per generation.
- Notion 504 gateway_timeout: check the page before you retry
A Notion 504 gateway_timeout does not mean the write was undone. Read the page, write the Sume video URL once, and dedupe on the webhook's job_id.
- opencode mcp auth: sign in to Sume, list, debug, log out
Run opencode mcp auth sume to start Sume's OAuth consent, then list, debug or logout. v1.18.33 now reports browser launch failures and redacts debug output.
Written by Sume