Mariano Benedettini
07/28/2026, 1:43 PMkapa.ai
07/28/2026, 1:43 PMrequester:
type: HttpRequester
url_base: "https://api.example.com/v1/"
request_parameters:
team_id: "{{ config['teamid'] }}"
sort_order: "ASC"
$parameters This is a component-level configuration mechanism for passing values down through the component hierarchy â it does not directly set HTTP request parameters. Its purposes are: [Parameters]
1. Avoid repetition by defining a value once at a parent level and reusing it in child components.
2. Automatically populate component fields â if a parameter key matches a field name on a child component (like path on an HttpRequester), it is automatically assigned. [Auto Propagation]
3. String interpolation â values can be referenced via {{ parameters['MyKey'] }}.
streams:
shipping_rates:
$ref: "#/definitions/base_stream"
$parameters:
path: shipping_rates # automatically sets requester.path
name: shipping_rates # automatically sets stream.name
Can $parameters set request_parameters? Yes â indirectly. You can use $parameters to pass a value and then reference it inside request_parameters via interpolation:
outer:
$parameters:
my_filter: "active"
requester:
request_parameters:
status: "{{ parameters['my_filter'] }}"
Also, as seen in the Stripe connector, request_parameters itself can be passed as a $parameters value to propagate down to a requester: [Stripe manifest]
retriever:
$ref: "#/definitions/events_objects_retriever"
$parameters:
request_parameters:
types[]: '{{["charge.captured", "charge.updated"]}}'
Summary đ 0 button đ 0 button âšī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements