coupang-partners

n8n community node for Coupang Partners Open API - products, deeplinks and performance reports

Package Information

Released: 2 mo ago
Downloads: 4 weekly / 39 monthly
Latest Version: 0.2.0

Available Nodes

Documentation generating…

Documentation

n8n-nodes-coupang-partners

An n8n community node for the Coupang Partners Open API (쿠팡 파트너스).

Browse and search Coupang products, turn product URLs into tracked affiliate links, and pull click, order, cancel and commission reports into your workflows.

Installation · Credentials · Operations · Rate limits · Output · Compatibility

Installation

In n8n, go to Settings → Community Nodes → Install and enter:

n8n-nodes-coupang-partners

For a self-hosted instance you can also install it directly:

npm install n8n-nodes-coupang-partners

Credentials

You need an Access Key and Secret Key from Coupang Partners (파트너스 → 도움말 → Open API). Both are secrets.

Add them under Credentials → Coupang Partners API, then press Test — the node signs a real request against the Goldbox endpoint to confirm the key pair works before you build anything on it.

Every request is signed with HMAC-SHA256 over signedDate + method + path + queryString, so your server clock must be accurate.

Operations

Product (상품)

Operation Endpoint Notes
Get Best Products by Category GET /products/bestcategories/{categoryId} 19 categories in a dropdown, up to 100 results
Get Goldbox Products GET /products/goldbox Refreshed daily at 07:30 KST
Get Coupang PL Products GET /products/coupangPL Up to 100 results
Get Coupang PL Products by Brand GET /products/coupangPL/{brandId} 9 brands in a dropdown
Search Products GET /products/search Max 10 results, 50 calls/minute
Get Recommended Products GET /products/reco Personalised by ADID/GAID/IDFA

Link (링크)

Operation Endpoint Notes
Create Deeplink POST /deeplink Converts a list of Coupang URLs into tracked short links

Report (실적 리포트)

Operation Endpoint
Get Clicks Report GET /reports/clicks
Get Orders Report GET /reports/orders
Get Cancels Report GET /reports/cancels
Get Commission Report GET /reports/commission

Window: up to 30 days per request, data from 20181101. Refreshed daily at 15:00 KST.

Ads Report (광고 리포트)

Operation Endpoint
Get Impression/Click Report GET /reports/ads/impression-click
Get Ads Orders Report GET /reports/ads/orders
Get Ads Cancels Report GET /reports/ads/cancels
Get Ads eCPM Report GET /reports/ads/performance
Get Ads Commission Report GET /reports/ads/commission

Window: up to 14 days per request, data from 20211025.

Rate limits

Coupang suspends an account for 24 hours past roughly 30 calls per hour, and permanently after three suspensions. This is the single most important thing to know before automating against this API.

Practical consequences:

  • Do not put this node inside a tight loop or a minute-level schedule.
  • Return All on a report resource spends one API call per 1000 records. The node waits 1 second between pages by default; raise Options → Page Interval (Ms) if you are close to the limit.
  • Date ranges are validated locally, so an out-of-range window fails instantly instead of burning a call.
  • A 429 response is surfaced as an explicit rate-limit error rather than a generic HTTP failure.

Per-group limits documented by Coupang: search 50/minute, reports and ads reports 500/hour.

Output

Simplify is on by default and emits one n8n item per record, so you can pipe straight into a filter, a spreadsheet or a database without a Split Out node.

Operation Simplified output
Search Products One item per product, each carrying the shared landingUrl
Search Products with Search Page Link Only A single item holding just landingUrl
Get Recommended Products One item per recommendation (the API returns ~20, despite the docs showing one)
Everything else One item per row of data

Turn Simplify off to get the raw { rCode, rMessage, data } envelope as a single item.

Sub ID

Sub ID is the channel ID registered in Coupang Partners. Clicks on links generated without a registered Sub ID are excluded from commission settlement, so set it on any operation whose output you publish.

Date ranges

Report resources take a Date Range preset — Today, Yesterday, Last 7/14/30 Days — or Custom with two date pickers. Presets are computed in KST, matching how Coupang dates its reports.

Custom dates accept either a date picker value or a raw yyyyMMdd string. The day you pick is the day that gets queried regardless of the server timezone.

Troubleshooting

Symptom Cause
Specified key is not registered. (401) The Access Key is wrong, or the server clock has drifted. The HMAC signature covers a timestamp that Coupang validates, so a skewed clock fails authentication.
Forbidden (403) The Open API is not enabled for this Partners account, or the account is serving a 24-hour suspension.
Coupang Partners rate limit exceeded (429) Stop the workflow. Three suspensions make the ban permanent.
Coupang allows at most N days per request Raised by the node before any call is made — narrow the date range.
url convert failed on Create Deeplink The product is delisted or the URL is not a Coupang product page. Returned as HTTP 200 with rCode 400.

Four things differ from the published API reference, all confirmed against the live gateway:

  • Authentication failures return 401, not the 403 the docs list.
  • Gateway errors use a { code, message, transactionId } body rather than the documented { rCode, rMessage }. The node reads both.
  • A 200 does not always mean success. Create Deeplink answers 200 OK with { rCode: "400", rMessage: "url convert failed" } for a delisted product, so the node checks the envelope on every response instead of trusting the HTTP status.
  • Get Recommended Products returns an array of about 20 products. The docs show a single object. The node decides the shape from the payload rather than the operation, so both work.

The example product URL in the API reference (184614775) is delisted and no longer converts.

Compatibility

Tested against n8n 2.33.7 and n8n-workflow 2.x. Requires Node.js 20.15 or later.

Local development

Symlink the built package into n8n's custom directory:

pnpm build
mkdir -p ~/.n8n/custom/node_modules
ln -sfn "$PWD" ~/.n8n/custom/node_modules/n8n-nodes-coupang-partners

Nodes loaded this way register under the package name CUSTOM, so a workflow JSON must reference the type as CUSTOM.coupangPartners rather than n8n-nodes-coupang-partners.coupangPartners. Installing through Settings → Community Nodes uses the full package name instead.

Development

pnpm install
pnpm build
pnpm test     # HMAC signing, date handling and response unwrapping
pnpm lint

pnpm test cross-checks the signature against the reference implementation in the API docs and asserts the category/brand tables still match the documented codes. It needs no API keys.

To verify against the real API, copy the env template and fill in your keys:

cp .env.example .env   # COUPANG_ACCESS_KEY / COUPANG_SECRET_KEY
pnpm test:live

pnpm test:live spends exactly 3 API calls — goldbox, search and deeplink — and prints the count before spending any of them. It covers the one thing the offline suite cannot: that a real 200 response unwraps into the items this node promises. Do not run it in a loop; the account-wide limit is roughly 30 calls per hour.

Upgrading from 0.1.x

0.2.0 changes the output shape and one input field:

  • Responses are split into one item per record by default. Set Simplify to off to restore the previous single-envelope output.
  • Coupang URLs on Create Deeplink is now a list. Existing comma-separated strings are still parsed, so saved workflows keep working.
  • Report start and end dates are now date pickers with presets. Raw yyyyMMdd strings are still accepted.

Resources

License

MIT

Discussion