n8n-nodes-sudomock) covers the render API, and n8n lists it as verified. From
inside a workflow you can upload a PSD, render it with new artwork and
personalized text, turn a product photo into a reusable mockup, remove a
background, check and fix the seams of a pattern tile, render a short product
video, and start a workflow the moment a render finishes.
How to use SudoMock’s n8n node
1
Install the node
Search for SudoMock in the nodes panel, or install the package
n8n-nodes-sudomock from the community nodes screen. The
listing on n8n carries the steps
for your instance. The node then appears in every workflow on it.2
Create an API key
Create a key in your dashboard
and copy it once. Keys begin with
sm_, and
Authentication explains where they are accepted.3
Add the SudoMock credential
In n8n, open Credentials, choose SudoMock API, and paste the key
into API Key. n8n checks it against your account on save, so a wrong key
fails at setup instead of halfway through a run.
4
Render your first mockup
Add a SudoMock node and pick the PSD Mockup: Render operation. Give
it a mockup UUID and a design URL. Upload a PSD
first if you do not have a template yet.
The finished image URL arrives on the node output at
data.print_files[0].export_path. Pass it straight to the next node.Operations
Pick an operation on the SudoMock node and n8n draws the fields it needs.
These are the names from version 0.12 of the node. PSD Mockup: Get Layers
comes with version 0.14, and Check Seams and Fix Seams with version
0.18. An instance still on an earlier version shows Render Mockup and
2D: names for the same operations; updating the node from Settings,
Community nodes brings the names in line.
Photo mockups describes that family.
Personalized text in the same render
PSD Mockup: Render carries a Text Layers field beside the artwork fields, so one node fills the artwork and the buyer’s name in a single call. An override names a text layer and supplies plain text or styled segments, and can set the font, size, color, stroke color, and how the text fits its box when it runs long. Text layers covers the shape of one, and Font: Upload From URL puts your own TTF or OTF in front of it. PSD Mockup: Get Layers lists every layer of a template with its UUID, including the layers inside its smart objects. Put some of those UUIDs in the Hidden Layers field of PSD Mockup: Render to leave those layers out of one render; the template itself does not change.Repeat a design as a pattern
PSD Mockup: Render takes Tile under a smart object’s Additional Options, and the artwork repeats as a pattern across the whole smart object. Custom Width and Custom Height are one tile, Fit Mode places the artwork inside each tile, and Position Top and Position Left set where the grid starts, so a tile needs a size. Tile Spacing leaves a gap between the tiles, from 0 to 100 percent of the tile: that percent of the tile width between columns, and of its height between rows. Render Video offers the same fields on the smart objects it fills. Photo Mockup: Render takes Tile and Tile Spacing in Placement on a saved print area and in Surface Placement on a surface. The size you set there is one tile: Fit, or Width and Height, on a saved print area, and Coverage, or Width and Height, on a surface. Before you turn on Tile, run Check Seams on the artwork. The check is free and shows a line where the copies meet before the render does, and Fix Seams repairs a tile that has one. Set Crop Aspect when the render places the artwork with fitcrop, so the check sees the same tile.
Pattern seams covers when a check applies.
Keep a print area’s id
Photo Mockup: Set Print Areas keeps an area’s id when that area carries its Print Area ID, so a workflow that stored the id keeps rendering to it after the area moves.Long renders and the Get Job operation
A render, an upload or a photo mockup sent with Run Asynchronously returns a job id right away, so a workflow never waits on the response. Follow it with the Get Job operation and branch on the status field.
The first three mean the work is still in flight, and the last three are
terminal, so a branch that stops on those three never loops forever. Get Job
also offers Wait for Completion, which polls until the job is terminal and
returns the result on one output. Render Video always runs asynchronously
and carries the same toggle. Fix Seams always runs as a job too: turn on
Wait for Result to get the fixed tile on the node output, or follow the job
id with Get Job. Each fix carries an idempotency key, your own from
Idempotency Key or one the node makes, so a retry of the same execution
returns the same job and is not charged again. The full shape is on the
job endpoint.
Start a workflow from a render event
The SudoMock Trigger node registers a webhook endpoint on your account when you activate the workflow, so a finished render starts the workflow instead of a schedule doing it. Choose the events you want in the Events field, or leave the list empty to receive every event, including ones added later.seam_fix.succeeded and seam_fix.failed start a workflow when a seam fix
ends, and seam_fix.succeeded carries the fixed tile at result_url and a
second fixed version, or null, at alternative_url. The trigger
checks each delivery’s signature before the workflow runs, and removes its
endpoint again when you deactivate the workflow.
The trigger delivers photo mockup events under their current names,
photo_mockup.ready and photo_mockup_render.succeeded among them. An
endpoint created by an earlier version of the node keeps the earlier spelling,
2d_mockup.ready, until Webhook: Update Endpoint re-pins it.
Webhooks maps each name to its payload.Use the node inside an AI agent
The SudoMock node is also available as a tool, so an AI Agent node can call it and pick the operation that fits the request in front of it. To give an agent the tools directly, without n8n in the middle, Connect an agent covers the MCP server.Example workflow: render a seasonal drop across every template
Automate Print-on-Demand Product Mockups with SudoMock API is a published template you can import and run. It is built for the week a collection goes live, when one artwork set has to reach every product you sell.- Google Drive watches a folder and fires when new design files land in it.
- SudoMock lists your PSD templates.
- The workflow builds every design and product pairing from those two lists.
- SudoMock renders the pairings one at a time.
- The finished URLs are written to a CSV, grouped by design and by product.
- Google Drive receives the CSV.
- An email goes out when the batch is done.
Every SudoMock operation reads the same credential, so one key is enough for a
whole instance.