Skip to content

Extractors

An extractor is attached to a chain step and pulls a value out of the step’s response into a named variable. That variable is then available to all subsequent steps in the chain via {{variableName}}.

[SCREENSHOT: Extractor configuration panel — type dropdown, expression field, variable name field]

FieldDescription
TypeExtractor type (protocol-specific, see below)
ExpressionWhat to extract (meaning depends on type)
Variable nameName of the variable to store the result in

Extracts the HTTP response status code as a string.

FieldValue
Expression(not used)
Example output"200"

Evaluates a JSONPath expression against the response body.

FieldValue
ExpressionJSONPath string, e.g. $.data.token
Example output"eyJhbGci..."

Returns the entire response body as a string.

FieldValue
Expression(not used)

Returns "true" if the SMTP exchange completed without any assertion failures, "false" otherwise.

FieldValue
Expression(not used)

Returns the server’s response lines for a specific command, joined as a string.

FieldValue
ExpressionThe command string to match (e.g. MAIL FROM:<sender@example.com>)

Leave the expression blank to match the server greeting exchange.


Returns "true" if all IMAP commands completed successfully.

FieldValue
Expression(not used)

Returns the untagged server lines for a specific IMAP command.

FieldValue
ExpressionThe command string to match (e.g. SEARCH UNSEEN)

Leave the expression blank to match the server greeting.


Returns "true" if the LDAP operation completed without assertion failures.

FieldValue
Expression(not used)

Returns the result code for a specific LDAP operation as a string.

FieldValue
ExpressionA prefix of the operation string (e.g. BIND cn=admin)
Example output"0" (success)

Stores a fixed value into a variable — useful for passing hardcoded values or defaults through the chain context.

FieldValue
ExpressionThe literal string value to store

Applies a regular expression to the value of another variable and stores the first capture group.

FieldValue
ExpressionRegex pattern with one capture group, e.g. token=([A-Za-z0-9]+)

The source for REGEX is the previous extractor’s output or a named variable — configure the input variable in the extractor settings.