Special Variables
Last updated
Last updated
Special variable indicating the specified return value from a formula block.
Examples:
run_history_id -> int | None
Contains the ID of the particular IntegrationRunHistory model that has been generated for the given integration run. This value can be useful for reporting and analytics purposes. Please note the value might be None
if integration run history persistence is disabled in the integration’s configuration.
Exposes a adapter config field to be overridden via Glyue Field Mappings. Override values will temporarily be used in place of the adapter config value for the Service Request.
Warning: values stored within the Glyue Field Mapping do not have the same encryption methods employed for the admin usage of adapter configs. Protect your secret keys!
Example
FIELD | VALUE |
---|---|
parameters:
status: Any
payload: Any
headers: dict
payload defaults:
default success: Integration {path_name} completed successfully
default failure: Error
parameters:
payload: Any
Input payloads are derived from the http request body or can explicitly set in hooks. Usage with callint has the user provide a payload to use for the integration.
Each of the components below exposes a field to provide pass an iterable to the component. See the examples for each.
Gives access to the parent integration's namespace from a child integration during a synchronous integration run. Asynchronous integrations have no reference to their parent integrations.
Builder Component | Field | Item | Index |
---|---|---|---|
__adapter_config__.username
test_user_not_secret
Service Request
sritem
sridx
Field Mapping
fitem
fidx
Validation Rule
vritem
vridx
Mask
mitem
midx