Skip to main content

Workflow Triggers: Opportunity Created & Opportunity Changed

Use Opportunity workflow triggers to automatically run actions when an opportunity is created or when an existing opportunity is updated.

Updated over 3 months ago

Who This Is For / When to Use

Use these triggers if you want to automate notifications, assignments, follow-ups, or record updates tied to opportunity lifecycle events.

Overview: Opportunity Triggers

Opportunity triggers monitor changes to opportunity records and enroll the associated contact into a workflow when conditions are met.

Kyrios supports two core opportunity triggers:

  • Opportunity Created – Runs once when a new opportunity is created

  • Opportunity Changed – Runs any time an existing opportunity is updated

Opportunity Created Trigger

What This Trigger Does

The Opportunity Created trigger fires immediately when a new opportunity is added.

Common uses include:

  • Notifying sales teams of new opportunities

  • Auto-assigning opportunities to users

  • Starting follow-up or qualification workflows

Step 1: Create or Open a Workflow

  1. Go to Automations > Workflows.

  2. Click Create Workflow or edit an existing workflow.

Step 2: Add the Opportunity Created Trigger

  1. Click Add New Trigger in the workflow builder.

  2. Select Opportunity Created from the Opportunities section.

  3. (Optional) Update the Workflow Trigger Name.

Step 3: Add Filters (Optional)

Filters restrict which opportunities trigger the workflow.

Available standard filters include:

  • Assigned to

  • Has Tag

  • In Pipeline

  • Lead Value

  • Status

You may also filter using Opportunity Custom Fields or Contact Custom Fields.

If no filters are added, every new opportunity will trigger the workflow.

Step 4: Add Workflow Actions

Define what happens after the opportunity is created, such as:

  • Sending notifications or emails

  • Updating opportunity or contact fields

  • Creating tasks or internal alerts

Step 5: Save and Publish

  1. Click Save.

  2. Toggle the workflow to Publish when ready.

Opportunity Changed Trigger

What This Trigger Does

The Opportunity Changed trigger fires whenever an existing opportunity is modified.

This includes changes to:

  • Status

  • Pipeline or stage

  • Assigned user

  • Custom field values

Step 1: Add the Opportunity Changed Trigger

  1. In the workflow builder, click Add New Trigger.

  2. Select Opportunity Changed from the Opportunities section.

Step 2: Add Filters (Recommended)

Because this trigger runs on any change, filters are strongly recommended.

Common filters include:

  • Status (e.g., when status changes to Won)

  • In Pipeline or pipeline stage

  • Assigned to

  • Lead Value

  • Opportunity or Contact Custom Fields

Without filters, the workflow will run on every opportunity update.

Step 3: Add Actions and Publish

Add the actions you want to run when the opportunity changes, then save and publish the workflow.

Common Use Cases

New Opportunity Alert

Trigger: Opportunity Created
Action: Notify sales team and assign owner

Stage-Based Automation

Trigger: Opportunity Changed
Filter: Pipeline Stage = Proposal Sent
Action: Send follow-up email

Reassignment Logic

Trigger: Opportunity Changed
Filter: Lead Value > threshold
Action: Reassign opportunity to senior rep

Common Issues and Fixes

Workflow triggers too often

  • Add filters to narrow when the trigger runs

  • Use specific status or pipeline stage conditions

Workflow does not trigger

  • Confirm the workflow is Published

  • Ensure the opportunity change matches filter conditions

FAQs

What is the difference between Opportunity Created and Opportunity Changed?

Opportunity Created runs once when the record is first created. Opportunity Changed runs every time an existing opportunity is updated.

Can I run multiple actions from one opportunity trigger?

Yes. You can add multiple actions to the same workflow.

If I move an opportunity to another stage, which trigger should I use?

Use Opportunity Changed and add a filter for the pipeline stage.

Are filters required?

No, but they are strongly recommended to prevent unnecessary workflow runs.

Did this answer your question?