Enrich WeChat and Xiaohongshu links in Feishu Base automatically
To fill a Feishu Base row from BeatAPI, add an automation that sends an HTTP request to BeatAPI and updates the record that triggered the automation. For example, when an editor pastes a WeChat article link into the editorial Base, the automation calls wechat_mp.v2.fetch_article_detail_h5 and writes the article title into the same row. Request engagement metrics separately, only for the articles you shortlist. Xiaohongshu image notes can use the same table once a relay step picks the matching note from the xiaohongshu.app_v2.get_image_note_detail response.
Create the columns Source, URL, Lookup status, Title, Request ID, Updated at and Reviewer notes. Test with one article your team knows, and check that the title lands in the original row and that the editor’s note is still there.
Set the trigger and HTTP action
In the Base, open the automations panel and add a trigger that fires when a record meets your conditions: URL is populated and Lookup status is Pending. Branch by Source, then add Send HTTP request to each branch. POST to https://api.beatapi.io/v1/social-data/call with the headers Content-Type: application/json and Authorization: Bearer <BEATAPI_API_KEY>. Keep the key in restricted automation settings or a protected relay; anyone who can see the request headers can see the key.
Choose a raw JSON request body. Replace the example value with the trigger’s URL field, inserted with the variable picker, and check that the variable outputs the URL as text.
The second request body reads a Xiaohongshu image note. For a video note, use the matching share-link action.
Map the response back to the triggering record
- WeChat article. Set the response type to JSON, and use a saved success sample to define the fields Feishu can reference. Check
status,request_idanddata.content.title, and confirm that the returned article matches the trigger URL. Add an Update record action that targets the triggering record ID, and map only the columns the automation owns. - WeChat engagement. When you need engagement, run
wechat_mp.v2.fetch_article_statsin a separate step with the sameurlandraw:true. Follow the metrics guide for the observed fields, visibility and observation times. Write a measured zero as 0. When a field is missing, leave the cell blank or keep the last known value with the value’s original observation time. - Xiaohongshu note. Detail objects appear under
data.data[].note_list[], and Feishu’s HTTP output can referencenote_list[]only as a whole array. Pass the response through a JSON-capable step (see the last section) that selects the note with the unique verified note ID and returns scalar fields for the update. When you start from a share link, check that the returned note matches the shared note. Send ambiguous matches to review and keep the existing cells.
An editor can replace the link while a lookup is running. Keep the record ID and the URL sent in the request together. Before updating, check that the row still contains the same URL. For example, if the row now links to Event B when Event A’s title arrives, leave Event B pending. If your automation can read the record again, add the URL check before Update record; otherwise, hold the result for editorial review.
What should a completed row look like?
Suppose an editor pastes a registration article and writes “Confirm the event date” in Reviewer notes. After a successful lookup, the same row shows “Autumn event registration guide” as Title, “Filled” as Lookup status, and the current request ID and timestamp. The editor’s note stays in place. If a later engagement lookup returns a read count of 0, write 0. If the read-count field is absent, leave the cell blank or keep the previous value with the previous value’s observation time, so the editorial team can tell a real zero from a missing value.
For 30 links in a week, the titles take 30 detail requests. Looking up engagement for eight of the 30 articles brings the total to 38 requests. See BeatAPI pricing for each action’s price.
Turn the Xiaohongshu array into fields Feishu can reference
For example, use n8n as the relay. From the Xiaohongshu branch, send the share link and verified note ID to an authenticated n8n Webhook node. Connect Edit Fields → HTTP Request → Code → Respond to Webhook. In Edit Fields, extract both fields from the webhook body and name the node Note input. In HTTP Request, use BeatAPI credentials, send the image-note body above and output only the JSON body. Feishu makes one relay call, and the BeatAPI key stays in n8n.
Set the Code node to Run Once for Each Item. In Feishu, define the response fields from the Code node’s flat output, for example {"title":"Example title","note_id":"example","request_id":"example"}. On success, update the triggering row. On failure, keep the existing values and mark the lookup for review.
Test the automation in four steps before relying on it:
- Run the same test row twice. Confirm that both runs update the same record and that Reviewer notes survive.
- Run a failed input, and check that the earlier title stays intact.
- After a timeout, find the original request’s outcome in the execution log before retrying.
- For an intentional retry, reset Lookup status to Pending.
Feishu HTTP actions and response mapping · Write from the Feishu CLI

