Set Variable allows you to capture a value from a response and store it in PalDock for later use. This works both within the current flow (e.g. passing values between requests) and afterwards (e.g. using the stored value in tracking/postbacks). The value is persisted in the database, so it remains available beyond the immediate integration run.
How mapping works
Source: where PalDock should read the value from
- Body: a field inside the response body
- Header: a response header
- HTTP code: the response status code (for example 200, 404)
- Query: a query parameter in the response URL
- Constant: a fixed value you type manually
Then:
- Key: the field name or path to read from the selected source. Example keys: leadId, url, result.leadIds.0.id, Location
- Value: the PalDock variable to write into. Use curly braces for variables, for example {external_id}, {redirect_url}
Rule of thumb
- Key is what you read from the response
- Value is where you store it in PalDock
Examples
Save leadId from the response body into {external_id}
- Source: Body
- Key: leadId
- Value: {external_id}
Save url from the response body into {redirect_url}
- Source: Body
- Key: url
- Value: {redirect_url}
Common mistakes
• Do not put {variable} into Key. Key is always the response field name or path.
• Do not put a response field name into Value. Value is always the PalDock variable you want to store into.
