Opportunity Created Trigger in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Opportunity Created trigger fires a workflow whenever a new opportunity lands in Sparkforge. Filter by pipeline, lead value, owner, or tags to route, notify, and assign automatically.

Use the Opportunity Created trigger to react when a new deal enters a Sparkforge pipeline. Notify reps, assign tasks, or branch by lead value — all without manual handoff.

What the trigger does

It fires once when an opportunity is created. From there you can filter by pipeline stage, lead value, assigned user, tags, status, or lost reason to route the right deal to the right action.

Trigger fields

Field	Description	Required
Assigned To	The user owning the opportunity.	No
Has Tag	Filter by one or more tags.	No
In Pipeline	Pipeline the opportunity belongs to.	No
Lead Value	Monetary value of the deal.	No
Lost Reason	Reason recorded when an opportunity is marked lost.	No
Status	Current opportunity status (New, Open, etc.).	No

Operators

Equals to — exact match
Greater than / Less than
Contains
Is Empty / Is Not Empty

How to configure

In the workflow builder, pick Opportunity Created as the trigger.
Name it descriptively, like High-Value Lead Opportunity Created.
Add filters that match the deals you want to react to:
- Assigned To — route by owner.
- Pipeline — scope to a specific pipeline.
- Lead Value — threshold by deal size.
- Tag — multi-select supported (Equals to / Not equals to / Any of / None of). You can stack multiple Tag filters for advanced rules.
Save and add the actions you want to fire.

Example: VIP deal alert

You want the sales manager pinged whenever a new opportunity comes in above $10,000.

Trigger: Opportunity Created
Filter: Lead Value greater than $10,000
Action: Notify the sales manager

The workflow makes sure high-value deals don't sit unattended.

Frequently Asked Questions

Does the trigger fire on stage changes too?

No. This trigger only fires on creation. Use Opportunity Status Changed or Pipeline Stage Changed for those events.

Can I trigger on multiple tags at once?

Yes. Tag filters support multi-select and you can add multiple Tag filters for layered rules.

What if Lead Value is empty?

Use the Is Empty operator to include those records, or Is Not Empty to exclude them.

Can I run different actions per pipeline?

Use one workflow per pipeline with the In Pipeline filter, or use a single workflow with branching conditions on pipeline.