You saved several pour-over coffee videos, but now cannot remember which one explained pouring too quickly. Rewatching everything takes time; asking an AI for a script produces generic advice. A small source-linked notebook can help.
TRMesh retrieves public post details. Your workflow connects the steps. Coze or another platform is suitable only if your current account supports HTTP requests and secure credential storage. This guide describes the data flow rather than assuming a particular version of its interface.
Define the note before adding nodes
Keep four groups: original link and time, author-provided description, your viewing observations, and your proposed next video. A description is not a transcript, and your observation is not the author's statement.
For a coffee video, useful observations might include showing the finished cups first, demonstrating one pouring motion, and an opportunity to film common mistakes. These are things you record while watching, not visual facts this API automatically extracts.
Make one link request work first
Test a public Douyin share link using the full URL and documented parameter below. Do not substitute a block of copied promotional text for a video identifier. Compare the result to the original video and inspect its availability and business status.
An HTTP response alone does not prove the post is available. Send empty, deleted or restricted results to a failure branch. Save the source and reason instead of asking the summarizer to invent a note.
Connect the workflow in this order
| Node | Input | Next step |
|---|---|---|
| Start | Public share URL | Bind it to the HTTP parameter |
| HTTP | GET, full endpoint, parameters and server credential | Inspect the raw response |
| Check and extract | Actual status and post data | Extract confirmed fields |
| Organize note | Description, link and viewing observations | Produce a draft idea note |
| Save | Confirmed note | Your sheet or notebook |
Store the Bearer credential in secret settings. The person submitting a video should not have to submit the key. Map fields from the response you actually received rather than copying JSON paths from another provider's tutorial.
Do not ask the AI to guess speech
Some descriptions contain only tags. Without actual captions or a separately produced transcript, the workflow cannot state what the speaker said. Audio transcription is a different processing step, not an automatic feature of this detail request.
Watch the video and add a few observations when needed. Then ask:
Using the description and my viewing notes, identify the topic, a useful presentation technique and a different angle for an original video. Distinguish source information from my observations. Retain the source URL. Do not invent a transcript or fill gaps with unsupported claims.
Before publishing, verify practical facts and use your own footage and wording. Research notes are not permission to reuse the original video.
Deliberately test a failure before saving automatically
Try a valid link, an invalid one and the valid link again. Expect a normal note, a clear failure and a duplicate notice or update. You should not get three seemingly successful new notes.
Use a confirmed post identifier for deduplication where available, with the URL for reference. A failed request must never reuse the preceding successful response.
Use the notebook to choose what to film
Look for a question that several videos approach but leave unclear. If they show how to pour but not what a mistake looks like, film a controlled comparison. Choose a demonstration you can actually produce before writing a title.
Topic inspiration: connecting Douyin data to Coze through an HTTP interface. These instructions use TRMesh and do not assume the original tutorial's audio fields exist here.
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/douyin/web/fetch_one_video_by_share_url
| Parameter | Type | Required | Meaning |
|---|---|---|---|
share_url |
string | Yes | Share link |
Run the Python example
Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.
import os
import requests
# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/douyin/web/fetch_one_video_by_share_url"
params = {
"share_url": "https://v.douyin.com/e3x2fjE/"
}
response = requests.get(
url, params=params, timeout=30,
headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload) # Inspect the actual response before mapping fields
Endpoint documentation · Free profile tool
API calls use your TRMesh account allowance. Check the endpoint price before running a script.
