Skip to content
This repository was archived by the owner on Jul 18, 2026. It is now read-only.

feat(instagram): capture taken_at on posts#78

Merged
volod-vana merged 1 commit into
mainfrom
volod/instagram-posts-taken-at
May 31, 2026
Merged

feat(instagram): capture taken_at on posts#78
volod-vana merged 1 commit into
mainfrom
volod/instagram-posts-taken-at

Conversation

@volod-vana

Copy link
Copy Markdown
Member

What

Adds real per-post capture dates to Instagram posts:

  • instagram-playwright.js — extract taken_at (taken_at / taken_at_timestamp) from the IG v1 feed media node, emit as ISO string.
  • schemas/instagram.posts.json — add taken_at: string to the scope schema.

Why

The Memory timeline needs real per-post dates. Without taken_at, every post lands on the collected-at timestamp and piles onto one day. This is the desktop/DataConnect path; the web/lite path (data-pipe Apify actor) maps the same field.

⚠️ Needs a maintainer step before deploy

  • Re-register the connector (register.cjs → registry.json checksum + artifact). I did not include a registry.json change: register.cjs in my environment rewrote the entry inconsistently with main (dropped sourceId/displayName/..., changed meta/connectors/meta/ paths), so the checksum bump should be done with the correct tooling/setup.
  • Register the updated schema to Context Gateway so PS accepts taken_at (the scope is strict). This is a prerequisite for posts to persist with dates from either path.

Scope

IG taken_at only — branched cleanly off main (Slack is separate in #77).

Extract per-post capture time from the IG v1 feed media node
(taken_at / taken_at_timestamp) and emit it as an ISO string on
instagram.posts, plus add taken_at to the instagram.posts schema.

Gives the Memory timeline real per-post dates instead of one
collected-at pile.
@github-actions

Copy link
Copy Markdown

Schema Health Check — Non-blocking inherited issues

41/47 scopes consistent | 6 inherited Gateway gap(s) | no new blocking issues in this PR

@volod-vana
volod-vana merged commit 37311a2 into main May 31, 2026
1 of 2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant