global/event-context
Event & seasonal context — identify upcoming events and cultural moments for a niche.
Category: global
Source: workflows/research/events.py
Input Schema
Section titled “Input Schema”| Field | Type | Default | Description |
|---|---|---|---|
lookahead_days | integer | 30 | How far ahead to look for events |
niche | string | "" | Content niche |
platform | string | "" | Target platform (optional) |
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
Section titled “Output Schema”| Field | Type | Default | Description |
|---|---|---|---|
event_context | object | — | Events, seasonal themes, and content angles |
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. |
Task Pipeline
Section titled “Task Pipeline”gather_event_context| Task | Description |
|---|---|
gather_event_context | Gather event context — delegates to SDK stage. |
Run-spec example
Section titled “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: global/event-context
# Optional fields — copy any line(s) under `input:` and uncomment to set:# How far ahead to look for events# lookahead_days: 30## Content niche# niche: ""## Target platform (optional)# platform: ""#
input: {}Run it locally:
fab-workflow --from-file my-run.yamlOr submit over the wire — the same file is the request body:
curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=global/event-context' \ -H 'Authorization: Bearer fab_xxx' \ -H 'content-type: application/yaml' \ --data-binary @my-run.yamlEvery 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.).
Warnings
Section titled “Warnings”- Task
gather_event_contexthas no Pydantic types — contract is opaque to consumers.