research/post-engagement

research/post-engagement — fetch metrics for a list of post URLs.

Category: research
Source: workflows/research/post_engagement.py

Input Schema

Field	Type	Default	Description
post_urls	string[]	—	List of social media post URLs to fetch engagement for. Supported platforms: Instagram (/p/, /reel/, /reels/, /tv/), TikTok (/@user/video/<id> and /t/<id>), X / Twitter (/status/<id>), YouTube Shorts (/shorts/<id> and youtu.be/<id>). URLs that don’t match any supported platform land in the errors list with reason=‘unsupported platform’.
regenerate	object	—	When set, this run is a regeneration. Workflows may read direction / keep / extra_instructions to modulate prompts; the engine persists parent_run_id and parent_variant_index as run lineage columns.
variants	integer	1	Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs.

Output Schema

Field	Type	Default	Description
errors	any[]	—	URLs that couldn’t be fetched, with the reason for each.
kind	object	—	Variant card shape: video / carousel / image / text. Surfaced on the per-variant entry of the run-output API and used by gallery UIs to pick the right layout.
results	any[]	—	Successfully-fetched engagement, one row per URL.

Task Pipeline

fetch_all

Task	Description
fetch_all	Fan out across all supplied URLs concurrently.

Run-spec example

Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.

workflow: research/post-engagement

# Optional fields — copy any line(s) under `input:` and uncomment to set:
# List of social media post URLs to fetch engagement for. Supported platforms: Instagram (/p/, /reel/, /reels/, /tv/), TikTok (/@user/video/<id> and /t/<id>), X / Twitter (/status/<id>), YouTube Shorts (/shorts/<id> and youtu.be/<id>). URLs that don't match any supported platform land in the ``errors`` list with reason='unsupported platform'.
#   post_urls: []
#

input: {}

Run it locally:

fab-workflow --from-file my-run.yaml

Or submit over the wire — the same file is the request body:

curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=research/post-engagement' \
  -H 'Authorization: Bearer fab_xxx' \
  -H 'content-type: application/yaml' \
  --data-binary @my-run.yaml

Every workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).