Action - Find Opportunity
The Find Opportunity action allows you to locate an existing opportunity linked to the contact that triggered the workflow, based on specific criteria.
In This Article:
Action Description
The Find Opportunity action searches for an existing opportunity linked to the contact who entered the workflow, matching the filters you specify. All filters are combined using AND logic, meaning all specified conditions must be met to return a match.
If multiple opportunities satisfy these conditions, only one will be returned. You can choose to find either the Earliest (first created) or the Latest (most recently created) matching opportunity for that contact. Once found, this opportunity record becomes the reference for all subsequent opportunity-based actions in your workflow.
If no match is found, the workflow continues along a separate “Opportunity Not Found” branch, enabling you to handle that scenario differently (e.g., create a new opportunity).
Important: If there is no contact in the workflow (for example, in the case of an inbound webhook that does not include contact information), you must configure the Find Opportunity filters to map certain fields to the webhook parameters. Otherwise, the action will not be able to locate an opportunity.
Action Details
Value Name |
Description |
Mandatory |
|---|---|---|
| Action Name | A custom label to help you identify this step in your workflow. | Yes |
| Opportunity to be Found | Determines whether to retrieve the Earliest (first created) or Latest (most recently created) opportunity that meets the filter criteria for the contact entering the workflow. | Yes |
| Filters | One or more conditions to narrow down the search. All filters use AND logic. So all conditions much be true for the opportunity to be found. No limit to the number of filters. Filters can reference any standard or custom opportunity field (e.g., Opportunity Name, Followers, Status). If there is no contact (e.g., inbound webhook), filters must map certain fields to webhook params. Internal actions that do not involve a third party will have contact data associated with them. |
Yes |
| Multiple Matches | If multiple records match, only one opportunity is returned—either the earliest or latest, depending on your choice. | — |
| Branching Behavior | If an opportunity is found, the workflow follows the Opportunity Found path. If no match is found, it follows the Opportunity Not Found path. | — |
Example
Scenario: A new lead submits a form, and you want to check if an existing opportunity already exists for that lead. If it does, you update the opportunity; if not, you create a new one.
- Trigger: A contact submits a form on your website.
- Action: Find Opportunity
- Action Name: “Locate Existing Opportunity”
- Opportunity to be Found: Latest Opportunity
- Filters(all conditions must be met):
- Opportunity Name → Contains → “Contact_Email_Address”
- Status → Is → “Open”
- Branching:
- Opportunity Found: Proceed with an Update Opportunity action to modify fields such as Status or add notes.
- Opportunity Not Found: Proceed with a Create Opportunity action to add a new record to your pipeline.
This ensures you’re always referencing the correct existing opportunity if one is available, and only creating a new one when necessary.
Note: If no contact is present (e.g., from an inbound webhook without contact info), ensure your filters map relevant fields to the webhook data. Internal actions that do not involve a third party will have contact data associated with them.