hooks/from-research

Hooks from Research — generate hooks from a previous deep-research run.

Category: hooks
Source: workflows/hooks/from_research.py

Input Schema

Field	Type	Default	Description
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.
research_run_id	string	""
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

No schema defined.

Task Pipeline

fetch_research_output → bridge_research_to_hooks → generate_hook_ideas

Task	Description
fetch_research_output	Load the output of a completed deep-research run via the Fabric HTTP API.
bridge_research_to_hooks	Transform deep-research output into hook-generation input.
generate_hook_ideas	Generate hook ideas — delegates to SDK stage (70/20/10 strategy, PromptExtension).

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: hooks/from-research

# Optional fields — copy any line(s) under `input:` and uncomment to set:
#   research_run_id: ""
#

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=hooks/from-research' \
  -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.).

Warnings

• Last user task generate_hook_ideas has no Pydantic return type — workflow output schema is null. Declare a WorkflowOutput subclass and pass it to Flow(output=…) for a strict contract.
• Task generate_hook_ideas has no Pydantic types — contract is opaque to consumers.