> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How can I find Xiaohongshu notes in n8n and hand selected records to Feishu?

> Search Xiaohongshu notes from an n8n HTTP Request step, keep a reviewed queue in a Data Table, and update approved notes in a Feishu table by note ID.

To get a weekly shortlist of camping coffee notes into Feishu for review, run a BeatAPI search from an n8n HTTP Request step with `xiaohongshu.app_v2.search_notes`, verify the returned notes, then update Feishu records by note ID. For an image note you already selected, start from the note's share link with `xiaohongshu.app_v2.get_image_note_detail` instead.

## Start with one search in n8n

In your n8n workflow, add a keyword input and an HTTP Request step. Send a POST to `https://api.beatapi.io/v1/social-data/call`, store the BeatAPI Bearer key in n8n credentials and set the JSON body:

```json
{"action":"xiaohongshu.app_v2.search_notes","params":{"keyword":"露营咖啡","page":1}}
```

Check the gateway status and the application status, then identify useful notes. The [search exporter](/guides/xiaohongshu-notes-research) documents the verified `data.data.items[].note` path. Build rows from `data.data.items[].note`, or run the search exporter on saved responses. Keep the query, time, original response and request ID. Continue to later pages with the documented search session. Decide the collection scope before you enable a trigger in your own workflow.

## Add a weekly schedule and review queue

Start with **Manual Trigger → Edit Fields → HTTP Request → Split Out**. Set `keyword` in Edit Fields and bind `keyword` in the JSON body expression. When the HTTP Request node outputs the JSON body only, split `data.data.items` in **Split Out**. Check the success state and the array shape before splitting. End an empty run normally, and log the empty run's request ID separately from failed runs. Skip ads and entries that contain no verified note.

Store `note_id`, first and last observation time, request ID and review state in an n8n **Data Table**. Look up existing rows by note ID, and update the observation fields without overwriting the selection reason. Mark newly discovered candidates for review, and send only approved rows to Feishu. Replay a saved response and verify that no row is duplicated and that the reviewer's decision survives. Then switch to **Schedule Trigger**, set the workflow timezone and publish the workflow. Start each scheduled search at page one, and fetch additional pages only with the current run's search session.

To enrich a link from the Feishu side, use [Feishu Base record enrichment](/guides/feishu-base-social-enrichment).

Suppose a reviewer selected note N01 last week because N01 clearly shows grinding and brewing. If N01 appears again this week, update N01's last-seen time and request ID, and keep the selection reason. Put the new note N02 on a separate row, and wait for approval before sending N02 to Feishu. Comparing the N01 and N02 rows shows whether the scheduled search reused the existing record.

## Hand verified notes to the Feishu table

Give the Feishu table columns for note ID, link, title, source, observation time, selection reason and retrieval state. Update existing rows by note ID, and keep editorial notes in separate columns. Test the field mapping with one saved record, and verify that an update keeps the original review. If an update fails, keep the previous values and record the failed attempt.

With a confirmed image-note share link, send the following body to the same POST endpoint to enrich the note's row:

```json
{"action":"xiaohongshu.app_v2.get_image_note_detail","params":{"share_text":"<confirmed_image_note_share_link>"}}
```

Find the matching note in `data.data[].note_list[]` and write the title or detail text actually returned. For a video note, follow the [share link contract](/faq/xiaohongshu-share-links). Keep missing metric states, and verify the note's identity when a response contains multiple objects.

Write to Feishu through your authorized writing workflow or an existing table import. If your automation uses HTTP and record-update steps, verify that both steps can reach the mapped fields and the target record. Run one search and one row update end to end first, then check [data request pricing](https://beatapi.io/pricing) for the planned keywords and pages.