Use Picsart nodes to process images within n8n workflows. The package @picsart/n8n-nodes-picsart-creative-apis has evolved beyond the two-action version described in the original guide. Check the installed version and its available nodes before following older screenshots or field names.
Before you start
- An n8n Cloud or self-hosted instance with permission to use the required nodes.
- An instance owner or administrator to install community nodes.
- A Picsart account and the credentials required by your installed node version, with sufficient credits for the intended actions.
Install the node
Verified-node route: open the canvas nodes panel, search for Picsart and inspect the matching community node. If the intended node is available, an owner/admin can install it. Follow n8n’s verified-node instructions.
Self-hosted npm route: open Settings → Community nodes → Install and enter @picsart/n8n-nodes-picsart-creative-apis. Review the package and permissions, install the intended version and restart only if required by your deployment. The package metadata checked on November 6, 2026 lists version 5.4.8 and Node.js ≥20.15. Use the requirements for the version you install.
Do not substitute a similarly named GenAI or video package without reviewing its credentials, operations and output contract.
Connect credentials
Create the Picsart credential requested by the node. For an API-key credential, obtain the key from the intended Picsart account, store it in n8n’s credential settings and select that credential on the node. Follow any different authentication flow exposed by the installed version. Keep keys out of workflow text, image URLs and shared exports.
Build an image workflow
- Choose a trigger: a webhook can receive an image URL, a storage node can retrieve a file, or a database/spreadsheet row can provide its URL.
- For an operation expecting an image URL, provide a retrievable URL. If the trigger supplies binary data, use an operation that accepts it or upload it to controlled storage and supply a suitably scoped URL valid long enough for processing.
- Choose the background-removal operation. Map the image input and, where offered, select transparent, solid-color or image-background settings.
- For enhancement/upscaling, select the operation and only the factors and formats it exposes. The old guide listed 2×, 4×, 6×, 8× and 16×; those are not a universal factor list for every endpoint. JPG, PNG and WebP availability also depends on the operation.
- Inspect the node’s result. The older guide described binary image output plus JSON containing a URL and credit usage; verify the actual property names and fields in your installed version.
- Map the output to storage, an HTTP step or a Webhook Response. Keep the original separately.
Test and activate
Run one image through the complete workflow and inspect the final saved output. Check credentials, input accessibility, credits and errors. Activate the workflow only after it succeeds and monitor the first live runs.
If an operation is not available as a node action, an HTTP Request node can call the appropriate API contract. Keep Creative APIs v1 authentication and fields separate from newer model-based API instructions.
References: Picsart on n8n, official package, and community-node installation.