Template Variables

Template variables let you inject dynamic, runtime data into action parameters. They use double-curly-brace syntax and are resolved at execution time when the rule fires.

Syntax

Variables are written as {{variable.name}} inside any action param string value.

params:
  text: "The result is {{condition.result}} as of {{now}}"

Available Variables

Variable Details

{{condition.result}}

Contains the value that was evaluated by the condition check. This is the actual data point retrieved from the provider.

• For pr.age with operator gt and value 3: if the oldest PR is 5 days old, {{condition.result}} is "5".
• For billing.mtd with operator gt and value 50: if the spend is $72, {{condition.result}} is "72".

{{org.owner.email}}

The email address of the organization owner who set up the TinyOps workspace. Useful for routing notifications to the right person without hardcoding email addresses.

{{rule.name}}

The name field from the rule definition. Useful for identifying which rule generated a notification, especially when multiple rules share the same action channel.

{{now}}

The current UTC timestamp in ISO 8601 format when the action executes. Useful for audit trails and time-stamping notifications.

{{trigger.data}}

The raw event payload that caused the trigger to fire. For webhook triggers, this contains the full incoming event data. For schedule and poll triggers, this may be minimal or empty.

Usage in Action Params

Template variables work in any string value within the params object. They can be combined with static text and used across all action providers.

Slack Message Example

name: stale-pr-alert
 
trigger:
  type: schedule
  cron: "0 9 * * 1-5"
 
condition:
  provider: github
  check: pr.age
  operator: gt
  value: 3
  repo: acme/webapp
 
action:
  provider: slack
  method: send_message
  params:
    channel: "#engineering"
    text: |
      *Stale PR Alert*
      Rule: {{rule.name}}
      Oldest PR age: {{condition.result}} days
      Checked at: {{now}}
      Owner: {{org.owner.email}}

Email Example

name: weekly-repo-summary
 
trigger:
  type: schedule
  cron: "0 9 * * 1"
 
condition:
  provider: github
  check: repo.open_prs
  operator: gt
  value: 0
  repo: acme/webapp
 
action:
  provider: email
  method: send
  params:
    to: "{{org.owner.email}}"
    subject: "Weekly summary: {{rule.name}}"
    body: |
      Hello,
 
      Your weekly repository summary is ready.
 
      Open PRs: {{condition.result}}
      Generated: {{now}}
 
      - TinyOps

GitHub Comment Example

name: large-pr-warning
 
trigger:
  type: webhook
  event: github.pull_request.opened
  source: github
 
condition:
  provider: github
  check: pr.lines_changed
  operator: gt
  value: 500
 
action:
  provider: github
  method: pr_comment
  params:
    body: |
      ## Large PR Detected
 
      This PR has **{{condition.result}}** lines changed (threshold: 500).
 
      Please consider splitting this into smaller pull requests for easier review.
 
      _Automated by {{rule.name}} at {{now}}_

Webhook Payload Debugging

name: release-notification
 
trigger:
  type: webhook
  event: release
  source: generic
 
action:
  provider: slack
  method: send_message
  params:
    channel: "#releases"
    text: "Release event received at {{now}}. Payload: {{trigger.data}}"

Multiple Variables in One String

You can combine any number of variables in a single param value:

params:
  text: "[{{rule.name}}] Alert at {{now}}: value is {{condition.result}}. Contact {{org.owner.email}}."

Variables by Provider Context

Next Steps

• Actions for all available methods and params
• Conditions to understand what {{condition.result}} contains
• YAML Syntax for complete rule structure