See llms.txt for all machine-readable content.

Back to Templates

Inspect Vinted listings and log results with Google Sheets, Slack, Notion or email

Created by

Created by: Advisync || advisync
Advisync

Last update

Last update a day ago

Categories

Quick overview

Inspect bounded Vinted listing samples, then preview rows or a short summary for Google Sheets, Slack, Notion or email. Choose Ralph Lauren, Dior, Sezane or a custom search. The default first execution prepares input without credentials, source requests or destination writes.

How it works

  1. A manual trigger reads eight common customer fields; a separate Advanced controls node retains source modes, approval phrases and lowerable resource ceilings.
  2. With no completed run ID, AUTO prepares the selected search and returns a readable configuration receipt without HTTP, credentials or writes. A matching completed run ID selects recovery; AUTO never starts a paid search.
  3. For listing previews, three Apify read nodes verify the exact Actor/build, terminal status, original stored input, resource and cost guards, then validate the versioned results payload.
  4. The workflow removes exact duplicate source rows, preserves partial/capped warnings and prepares full listing receipts for Sheets or a bounded digest for the other destinations. Asking prices do not establish sale value or profit.
  5. PREVIEW displays the selected target and proposed content, then stops before every destination writer. A separate explicit approval is required for any write or delivery.
  6. The Sheets path reads before writing, appends missing observation receipts, verifies them and writes the run completion marker last. An exact completed replay is designed to skip duplicate writes.
  7. Slack, Notion and email use a durable n8n Data Table intent before one provider call and verify the provider receipt. Unresolved attempts stop for manual reconciliation. Run executions serially: the journal does not guarantee concurrent exactly-once delivery.

Setup

  1. Import into a new empty workflow and keep manual execution. Open node 01, choose one preset and destination, and leave the completed run ID blank. Execute once and read node 02B. No credential is required for this first configuration check.
  2. To preview actual listings, supply your own matching completed Actor 0.13.69 run ID and one destination target. A standard Google Sheets or Notion page link is accepted; Slack uses one channel ID, and email uses one sender and recipient.
  3. For recovery, select your own Apify Bearer Auth credential only on read nodes 04B, 07A and 08A. Leave paid-start node 04A unbound. Keep Advanced write_mode=PREVIEW and inspect the target, proposed content and partial-result warnings.
  4. For later Sheets writes, create Vinted Listings and Vinted Runs tabs with the exact headers in the canvas note, then connect your Google Sheets credential to the listed Sheets nodes. Use the Advanced write controls only after reviewing a preview.
  5. For later Slack, Notion or SMTP delivery, connect only the selected service credential and create the n8n Data Table with the exact string columns in the recovery note. Set its ID and the destination-specific approval phrase in Advanced controls.
  6. Starting a new Actor run is optional and separate: explicitly choose START_BOUNDED_RUN, bind 04A and enter its exact approval phrase. The fixed ceilings are USD 0.25, 40 listing rows and 45 total source requests. Reuse completed runs for recovery instead of starting another collection.

Requirements

  • n8n with Manual Trigger, Set, Code, If, HTTP Request and the selected service nodes; Data Table is needed for Slack/Notion/email delivery.
  • An Apify account and your own credential are needed only when retrieving or starting a source run. This template fixes source build 0.13.69 and payload contract 0.13.0.
  • Use customer-owned service credentials and one exact destination. No owner credentials or real destination IDs are embedded.

Customization

  • Choose one of three presets, or select custom and set query, optional size and maximum asking price in node 01. Simple custom searches default to buyer/France; goal and countries remain editable in Advanced.
  • Paste the selected destination link or ID into destination_target. Conflicting common and Advanced targets stop before HTTP. Other destination targets are cleared from the resolved configuration.
  • Lower resource ceilings in Advanced. Keep previews enabled until the proposed rows or digest and its exact target have been reviewed.

Additional info

This unofficial Actor supports listing inspection, not purchases, sold-price estimates, seller-country identification or profit forecasts. France has bounded source-validation evidence; broader reliability is unproven. Partial/capped results must remain visibly partial. Source cost controls are requested ceilings; platform settlement can slightly exceed them. Native compact configuration preparation was verified in n8n Cloud; actual listing preview and each provider delivery for this exact revision remain separate qualification gates. Provider acceptance does not prove recipient delivery or reading. Keep executions manual and serialized; reconcile unresolved journal attempts rather than blindly resending.