Get Douyin user published videos and first video details with JustOneAPI

Use this n8n workflow to get published videos from a Douyin user and fetch details for the first video with JustOneAPI.

Who’s it for

This template is for creator research teams, marketing teams, creator operations teams, analysts, and automation builders who want to inspect a Douyin account’s published videos and collect the first video’s detail data in a reusable n8n workflow.

What this workflow does

The workflow starts from a Douyin secUid and sends a request to the User Published Videos V3 endpoint. It keeps the raw video list response, extracts video IDs from data.aweme_list, selects the first unique aweme_id by default, then requests video details with the Video Details V2 endpoint.

The workflow returns both the selected video from the list and the detailed video data in a structured format, while also keeping raw outputs for inspection and troubleshooting.

This makes it useful for account monitoring, video research, content archiving, creator analysis, and building downstream reporting workflows.

What you need

• A JustOneAPI token
• A Douyin user secUid
• An n8n environment with HTTP Request node support

Set up

1. Import the workflow into n8n.
2. Open the Prepare API and User Data node.
3. Add your JustOneAPI token.
4. Enter the Douyin user secUid.
5. Leave maxCursor as 0 for the first request, or set it if you want to continue from a previous page.
6. Leave maxVideos as 1 if you want to fetch details for only the first unique video by default.
7. Run the workflow and review the final output node.

How it works

1. Prepare the API base URL, token, user secUid, pagination cursor, and video limit.
2. Request the user’s published video list from Douyin User Published Videos V3.
3. Keep the raw video list response for debugging.
4. Extract videos from data.aweme_list.
5. Select the first unique video ID from aweme_id.
6. Request the selected video’s details from Douyin Video Details V2.
7. Build a final output with structured video list data, selected video data, video detail data, pagination data, and raw API responses.

Output

The final output can include fields such as:

• requestedSecUid
• requestedMaxCursor
• videoRank
• selectedBy
• videoId
• videoDetail
• selectedVideoFromList
• videoListSummary
• pagination
• rawVideoListOutput
• rawVideoDetailOutput

The structured video detail output can include fields such as:

• videoId
• desc
• previewTitle
• createTime
• groupId
• secItemId
• shareUrl
• shareTitle
• shareDescription
• mediaType
• awemeType
• isMultiContent
• imageCount
• coverImage
• originCoverImage
• videoWidth
• videoHeight
• videoDuration
• playUrl
• downloadUrl
• authorUid
• authorSecUid
• authorNickname
• authorSignature
• authorUniqueId
• musicId
• musicTitle
• musicAuthor
• musicPlayUrl
• diggCount
• commentCount
• shareCount
• collectCount
• playCount
• allowComment
• allowShare
• allowDownload

Notes

• This workflow is built around the Douyin User Published Videos V3 and Video Details V2 endpoints.
• It selects the first unique aweme_id from data.aweme_list by default.
• It keeps both raw API responses so you can inspect the original returned data.
• You can increase maxVideos if you want to extend the workflow to process more than one video.
• You can connect the final output to Google Sheets, Airtable, Notion, databases, alerts, dashboards, or other n8n workflows.