agenthub · config.fetch
Config Fetch
Load this org's configuration — business name, contact line, industry — and hand it to a Prompt Template as variables.
Why the node earns its place
It is what makes one published agent serve many businesses. The prompt says {{name}} and {{contact_str}}; this node fills them per org, keyed by the release actually running and the org running it.
Failure is deliberately quiet. On a missing row or an error it returns nothing and the agent continues — with the literal placeholders visible in the prompt, which is a clear signal that configuration is missing rather than a crashed chat.
How it works at run time
- 1Resolve the running release and the org.
- 2Read that pair's configuration.
- 3Emit it as
variables, ready for a Prompt Template's variables input. - 4On anything missing or broken, return empty and let the chat continue.
What you wire
Inputs
Nothing to wire in.
Outputs
- variablesobject
Configuration
Nothing to configure — this node has no settings of its own.
What usually goes wrong
Watch for this
An agent greeting someone as {{name}} is this node returning nothing — the configuration row for that org and release does not exist. It is not a prompt bug, and Prompt Template's completeness guard will not catch it either, because the variables were supplied, just empty.
Behaviour & provenance