n8n Pinterest API: Build a Source-Linked Content Research Sheet

An n8n Pinterest API workflow can turn a focused search into a source-linked content research sheet. This guide retrieves one page of public Pinterest search results through Nexscope and prepares up to 20 Pin rows for review. It keeps Pin identity separate from destination links so you can investigate content patterns without mistaking repeated Pins for independent demand.

Quick answer: Import the inactive manual starter, select your own HTTP credential and inspect the mapped output before enabling the disabled Sheets writer. Keep source IDs, URLs, resource states and missing fields with the evidence.

Reviewed November 5, 2026 against public contracts, official platform documentation and production-account API tests. Vendor-authored tutorial. The dated example below records real paid API observations; n8n/Make platform import, live Sheets writes and AI drafts were not executed.

What question should the Pinterest search answer?

Define a content problem that a reviewer can inspect. “Small kitchen coffee station” can support a study of storage layouts, product demonstrations and space constraints. It cannot establish an official keyword search volume. Record the search phrase and the buyer situation before opening results, then decide which examples actually answer that question.

Use the starter body with keyword and trim. There is no cursor in the first request and no automatic page loop. A useful first review can be smaller than a complete collection: the goal is to decide whether a theme deserves further work. The local cap of 20 rows controls the worksheet size after retrieval; it is not an upstream search limit.

Production-account test: what actually returned?

A retained production-account sample used small kitchen coffee station storage and trim: true. It returned 16 Pins at 07:14:06 UTC on November 5, 2026, with AVAILABLE state and hasMore: true. The response reported a settled 10-credit charge, confirmed in the account credit ledger.

This sample is useful precisely because the destination and save-count fields were unavailable. Keep those cells empty with missing-field markers. Do not infer destination-domain diversity from Pin URLs or convert missing saves into zero popularity. The Pin links remain review leads; a human would need to inspect destinations before making a source-diversity claim. The original shorter query was a separate completed call whose response was lost when the browser restarted; it is not included as a second data sample here.

These are observations from Nexscope Online test using an existing production account. They validate the API example, not a complete execution inside n8n. See the sanitized live-case record for inputs and selected fields. Counts, availability and prices can change.

• Download the tested pinterest request JSON

These request files contain the real public inputs used for the dated case, without credentials. Executing them again can consume credits.

How do you import and configure the n8n starter?

Import the workflow JSON into your own n8n instance and configure it before executing. It uses core Manual Trigger, Code, HTTP Request and Google Sheets nodes. The workflow is inactive, has no schedule and disables the Sheets writer. The HTTP nodes do not retry automatically. This is a Nexscope-authored HTTP workflow, not a claim of a native platform integration.

1. Edit Research input with a real input and inspect the JSON body below. Placeholder handles, video IDs and page IDs must be replaced.
2. Create an HTTP Header Auth credential: header name Authorization, value Bearer YOUR_ACTUAL_KEY. Select that credential on each Nexscope HTTP node. Keep the key out of Code nodes, request files and exported workflow JSON.
3. Leave Sheets disabled. Run manually only when ready for the stated API calls, then inspect the HTTP response and Validate and map output.
4. Create a scratch spreadsheet using the companion CSV headings. Select your Google credential, spreadsheet and sheet in the disabled writer; its configured cell format is RAW.
5. Enable the writer only after checking the mapped rows. Append can duplicate records on another execution; no cross-run lookup is included.

The mapping preserves zero and false values, records missing fields and escapes text that could be interpreted as a spreadsheet formula. Review your installed node versions if n8n requests a migration. The download has no saved credentials or pinned sample data.

Request body

POST https://api.nexscope.ai/pinterest/search

{
  "keyword": "small kitchen coffee station",
  "trim": true
}

How do you distinguish Pins from destinations?

A Pin URL and its outbound source URL answer different questions. The Pin identifies the item returned by the API. The sourceUrl points to a destination when supplied. Several Pins can link to the same article, product or storefront. Preserve both instead of replacing one with the other.

The mapping uses data.items and requires a source ID and HTTPS Pin URL for every exported row. It keeps title, description, destination URL and available save count. Empty destination links remain empty with a missing-field marker. Do not generate an imagined destination from a title or assume that an image’s host owns the underlying content.

How do you build a useful research sheet?

Add interpretation after the retrieved fields. Suggested review columns include room constraint, visual format, buyer question, repeated destination domain and possible content angle. Read the linked source before calling a Pin a tutorial: a visually appealing image can lead to a product page, an unrelated page or an unavailable destination.

Group results in two ways during review. Pin identity helps prevent duplicate rows within a response. Destination identity helps reveal when apparently diverse examples come from one source. The starter only deduplicates repeated Pin IDs within the current execution; it does not normalize destination tracking parameters or maintain a cross-run database. Any domain-level grouping should preserve the original URL for traceability.

Field mapping checkpoint

Node order: Manual Trigger → Research input → HTTP Request → Validate and map → disabled Sheets writer.

What can save counts and repeated themes tell you?

They can guide further reading, with clear limits. Save counts may be missing and are not equivalent to purchases. A theme appearing repeatedly in a selected result page is not a market-share estimate. Search ranking and repeated destinations can shape the sample, so review less prominent and contradictory examples too.

For a coffee-station brief, record which constraints are actually visible: narrow counter, wall storage, appliance clearance or renter-friendly setup. Distinguish an observed feature from a proposed design idea. If an AI step later groups themes, provide Pin IDs and destination links and require a reviewer to verify its groups. The downloadable starter contains no AI step and does not reuse source images.

How do you move from research to an original article?

Use the sheet to find a question you can answer with your own evidence. For example, a repeated space constraint can become a measured layout comparison using original dimensions and photographs. Citing a source does not grant permission to copy its images, descriptions or layout. Check content rights before reusing any asset.

Keep research and publication separate. The workflow neither creates Pins nor posts to a social account. If you want a brief grouped by topic rather than a row-per-Pin sheet, use the Make Pinterest brief workflow. In both cases, the reviewer should be able to trace every observation back to a returned source.

How do you control cost and handle failures?

Budget API calls, platform execution and optional AI separately. Inspect current Nexscope access and credit rules before running. In the retained November 5 tests, each API response reported 10 settled credits. That is an observed charge, not a permanent price quote. Pagination, retries and repeated manual runs can add calls. Local row or segment caps act after collection and do not define the supplier charge. An optional model request adds its own usage, and workflow-platform charging depends on your plan.

Stop on a business error, unexpected shape or unusable resource state and inspect the retained response. AVAILABLE and PARTIAL are different: label partial evidence rather than presenting it as complete. PRIVATE, RESTRICTED, NOT_FOUND, NO_TRANSCRIPT and UNKNOWN should not feed a speculative report. A failed downstream write does not justify blindly repeating the paid retrieval.

Keep returned collection dates separate from the client observation time; an older source timestamp is not fresh activity. Preserve pagination indicators when returned. API response cost, where present as processing time, is not a credit-price field. During these tests, Call Details showed “Not charged” for social calls while response usage and the account credit ledger showed charges. If those views disagree, reconcile the account credit ledger before assuming a call is free. Store credentials only in the platform’s credential manager and choose execution-log retention appropriate to the public content you collect.

Downloads and verification scope

• Inactive n8n workflow JSON
• Exact request body
• Review sheet headings

The n8n Code logic was exercised with constructed offline fixtures for valid, partial, empty and rejected responses. Graph checks confirm manual execution, absent embedded credentials, disabled Sheets writes and no automatic HTTP retry. Those offline checks do not establish compatibility with every installed n8n version. Live API access was checked separately for the dated example; the complete n8n workflow was not executed.

Read the underlying API and MCP research guide for broader source interpretation. These workflow articles focus on implementation; they do not promise search rankings, citations or campaign results.

Sources

• Nexscope: matching API contract — request and response fields reviewed for this guide.
• n8n HTTP Request documentation — HTTP node configuration.
• n8n Google Sheets operations — row operations and mapping.

Last reviewed: 2026-11-05 · Maintained by the official Nexscope team · Editorial & evidence policy.