Feature request: TikTok Accounts organic warehouse source
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Is your feature request related to a problem?
Marketing teams need to query their TikTok account and organic content data in the warehouse, separate from paid advertising data.
Requested source: TikTok Accounts. Priority: P2. Product use: Marketing.
Describe the solution you'd like
Add an account-authorized organic TikTok source. Start with account profiles and owned video records, with the metrics that the approved API provides. Keep TikTok Ads and TikTok Shop unchanged.
Access checks before implementation
- Confirm the API product, supported account types, app approval, permissions, token refresh, quotas, and permitted data use for a warehouse connector. Do not assume that Display API access permits the full analytics use case.
- Record the supported fields, history limits, update behavior, and deletion rules. Competitor schemas are references, not proof of our API access.
- Keep comments, replies, demographics, and detailed historical reports outside the first PR unless access and a specific requirement are confirmed.
Proposed PR scope
- PostHog/posthog — working source: add the source identity, configuration, registration, generated artifacts, and required migrations. Implement credential validation, schema discovery, and resumable imports through the shared REST framework. Use stable record keys. Refresh changing metrics without duplicate records. Define snapshot timestamps if metrics represent current values rather than historical facts. Add clear permission and reconnect errors, bounded retries, and rate-limit handling. Update
SOURCES.md. - PostHog/posthog.com — source documentation: document setup, required access, tables, sync behavior, history limits, and recovery steps. Connect the source's
docsUrlto the page. Coordinate publication with source release.
Reuse the existing source setup UI, sync status, and diagnostics. Do not add a new dashboard, a separate OAuth framework, or SDK changes. A complete, tested source should use the repository's alpha release convention; incomplete work must not appear as a working connector. Use a source feature flag if controlled access is needed.
Acceptance and security checks
- An authorized account can connect and complete an initial and a repeated sync. A resumed sync produces no duplicate records.
- Tests cover empty results, pagination, token expiry, revoked or missing permissions, rate limits, transient errors, and changing metrics.
- Security tests cover OAuth state validation where applicable, project access boundaries, and credential redaction from errors and logs. Capture no tokens or imported content in analytics.
- Use existing sync diagnostics to verify connection success, sync completion, and repeat-sync failures during rollout.
Describe alternatives you've considered
Manual exports or a custom REST source can provide a temporary path. TikTok Ads is not a substitute for organic account data.
Additional context
The supplied source list names this connector. The current source directory contains TikTok Ads and TikTok Shop, but no TikTok Accounts source. Searches of open and closed issues and PR titles found no matching organic account connector request.
References supplied with the request:
- https://docs.extract.to/sources/tiktok-accounts
- https://fivetran.com/docs/connectors/applications/tiktok-organic
Provider reference for the access check:
Implementation guide: .agents/skills/implementing-warehouse-sources/SKILL.md. Check current source and documentation conventions before coding.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .agents/skills/implementing-warehouse-sources/SKILL.md and inspect the existing TikTok Ads and TikTok Shop sources and current source directory conventions. First verify TikTok API access, permissions, supported fields, and history limits before choosing the implementation scope. Done means a tested, documented source with resumable repeat syncs, validation, error handling, security coverage, generated artifacts, migrations, and SOURCES.md updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100