Payload mappings

The Agent message action supports explicit mappings for its prefix and suffix. A mapping reads a value from the incoming trigger object.

Syntax

Mappings start with $trigger. followed by one or more object-key segments:

$trigger.release_header
$trigger.release.compare_url
$trigger.metadata.build-id

Each segment may contain letters, numbers, underscores, or hyphens. Array indexing, wildcards, functions, and implicit conversions are not supported.

Resolution

For $trigger.release.compare_url, Infra One reads:

{
  "release": {
    "compare_url": "https://github.com/example/repo/compare/v1...v2"
  }
}

The resolved value must exist and be a string. Missing paths, objects, arrays, numbers, booleans, and oversized strings fail before Slack posting.

Fixed value precedence

If Prefix from payload is present, it replaces Fixed prefix. If Suffix from payload is present, it replaces Fixed suffix.

Leave the mapping empty to use the fixed value. Leave both empty for no wrapper.

Limits

Trusted instructions may contain up to 20,000 bytes. Each fixed or resolved wrapper may contain up to 10,000 bytes. The completed generated message—including the test marker, prefix, generated body, and suffix—may contain up to 40,000 bytes.

Release example

The canonical release payload exposes:

• release_header as **Release 1.4.379**\n\n
• full_diff_footer as a Markdown link to the full GitHub comparison

Mapping those values keeps the heading and footer exact while the agent decides which changes deserve bullets.