Create your own workflow

Build custom workflows from scratch when templates don't meet your needs. Use the create your own builder to drag and drop actions from the actions catalog into automation that matches your process.

How to use this guide

This guide shows you how to build workflows using concepts and a complete example. Choose your learning path:

• Learn core concepts first: Read Core concepts and workflow patterns to understand the fundamentals, then apply them
• Follow the example: Jump to Example walkthrough to build an EC2 auto-resize workflow step-by-step
• Reference patterns: Use the workflow patterns section as a quick reference when building your own workflows

Why build custom workflows?

Build your own workflow to:

• Implement unique business logic that templates don't support
• Integrate multiple systems beyond standard templates
• Handle complex decisions with conditional branching
• Match your team's process for approvals and notifications

Core concepts

Understand these fundamentals before you build:

Syntax examples

Use these patterns when building workflows:

For detailed error handling patterns, see Best practices.

Quick start

Build your first workflow in five steps:

1. Navigate to one.newrelic.com > All Capabilities > Workflow Automation and select Create Your Own
2. Define parameters for credentials (from secrets manager: ${{ :secrets:keyName }}), configuration (regions, instance types), and runtime data (account IDs, alert IDs)
3. Drag actions from the catalog, connect them with ${{ .steps.stepName.outputs.field }} syntax to pass data
4. Insert switches for conditional branching, loops for processing lists or polling, approval gates for human decisions
5. Run after each section to catch errors early, then start or schedule your workflow

Key workflow patterns

Four essential patterns handle most automation scenarios. Each pattern is demonstrated in the example walkthrough below.

Conditional branching with switches

Use switches when: Outcomes vary based on data (threshold checks, API responses, user decisions)

Key syntax:

- name: hasCompleted
    type: switch
    switch:
      - condition: "${{ .steps.waitForCompletion.outputs.automationExecutionStatus == 'Failed' }}"
        next: displayError
      - condition: "${{ .steps.waitForCompletion.outputs.automationExecutionStatus == 'Success' }}"
        next: displaySuccess
    next: displayUnexpected  # Default path when no condition matches

Example: Handle team response, Verify and clean up

Loops for processing lists

Use loops when: Processing multiple items or repeating actions

For detailed information about loop structure, parameters, and advanced usage (including break/continue), see Loop structure.

Key syntax:

# Send progress updates using range loop
  - name: progressLoop
    type: loop
    for:
      in: "${{ [range(1; 5)] }}"  # Loop 5 times
      steps:
        - name: wait
          type: wait
          seconds: 10
        - name: progressMessage
          type: action
          action: slack.chat.postMessage
          version: 1
          inputs:
            channel: "${{ .workflowInputs.channel }}"
            text: "Resizing in progress..."

Example: Execute the resize

Approval gates and waiting

Use approval gates when: Human judgment is needed before destructive operations or compliance sign-off is required

Key syntax:

- name: requestApproval
    type: action
    action: slack.chat.postMessage
    version: 1
    inputs:
      channel: "#approvals"
      text: "Approve? React with :thumbsup: or :thumbsdown:"

  - name: getReactions
    type: action
    action: slack.chat.getReactions
    version: 1
    inputs:
      token: "${{ .workflowInputs.slackToken }}"
      channelID: "${{ .steps.requestApproval.outputs.channelID }}"
      threadTs: "${{ .steps.requestApproval.outputs.threadTs }}"
      timeout: 300  # Wait 5 minutes for reaction

  - name: checkApproval
    type: switch
    switch:
      - condition: '${{ .steps.getReactions.outputs.reactions | any(.name == "+1") }}'
        next: handleApproval
      - condition: '${{ .steps.getReactions.outputs.reactions | any(.name == "-1") }}'
        next: handleRejection

For simple delays:

- name: waitBeforeRetry
    type: wait
    seconds: 60  # Wait 60 seconds before continuing

Example: Request team approval

Passing data between steps

Use data passing when: One step's output becomes another's input (the foundation of all workflows)

Key syntax:

# Reference previous step outputs
  awsRegion: "${{ .inputs.region }}"
  instanceId: "${{ .steps.getAlert.outputs.data.entity.instanceId }}"

Example: All workflow steps

Variable assignment with assign

The assign step type allows you to initialize and assign values to variables that can be used in subsequent workflow steps. This step supports multiple data types including strings, integers, booleans, maps (objects), and lists (arrays).

Basic structure:

- name: <step_name>
    type: assign
    inputs:
      <variable_name>: <value_or_expression>

Example:

- name: variableInitialization
    type: assign
    inputs:
      stringVar: "${{ .workflowInputs.initialValue }}"
      intVar: "${{ .workflowInputs.anotherValue }}"
      concatenationVar: "${{ .workflowInputs.initialValue }} - concatenated"
      booleanVar: true
      mapVar:
        key1: "value1"
        key2: "${{ .workflowInputs.initialValue }}"
      listVar:
        - "listItem1"
        - "${{ .workflowInputs.initialValue }}"
        - "${{ .workflowInputs.anotherValue }}"
      statusCode: ${{ .steps.runAction.outputs.statusCode }}

Example walkthrough: Auto-resize EC2 with approval

This example builds a workflow that resizes EC2 instances when CPU spikes—after getting team approval via Slack. It demonstrates data gathering, conditional logic, external integrations, and error handling.

Workflow overview

High-level flow:

1. Gather data: Fetch alert and instance details from New Relic
2. Request approval: Send Slack message, wait for team response
3. Execute resize: Use AWS Systems Manager to resize EC2 instance
4. Verify and clean up: Check results, notify team, remove temporary resources

Prerequisites

Before building this workflow, ensure you have:

• AWS: Credentials with EC2 and Systems Manager permissions
• Slack: Bot token and channel for notifications
• New Relic: Alert condition monitoring EC2 CPU
• Secrets manager: Configured, see secrets manager

Build the workflow step-by-step

Build each part of the workflow. Each step includes specific actions and demonstrates workflow patterns.

Complete parameter reference

This workflow requires credentials, configuration, and runtime context as inputs. Sensitive values come from secrets manager using ${{ :secrets:keyName }} syntax.

Input categories:

• Authentication: AWS and Slack credentials
• Alert context: Account ID and issue ID from New Relic
• Configuration: Region, instance type, timezone, Slack channel

Next steps

After completing this example, explore these resources: