Find open opportunity

Identifier and availability

• Type: action
• Stable identifier: opportunity:find
• Status: Selectable — available in the new-node selector and importable.

Purpose

Finds the latest open opportunity for the current contact.

Prerequisites and context

It has no required configuration reference beyond its runtime context. A missing contact follows the not_found branch.

Parameters

Unknown parameter and settings keys are rejected. Resource references use names, emails, document keys, or endpoints rather than database IDs.

Inputs and available variables

Context exposed on found: opportunity.

Templated strings use double braces, for example {{contact.first_name}}. Availability in the editor does not create runtime context; the trigger and preceding branch still need to provide it.

Connections and branches

Connect this action into a root path with branch actions or into an existing branch using that parent’s token. It then terminates its current sequential path and exposes these exact, case-sensitive branch ports: found, not_found. Put following work inside those branches; do not place a sibling after this action.

Connection fragment:

{
    "from": "action_opportunity_find",
    "to": "next_action",
    "branch": "found",
    "order": 1
}

Valid JSON node example

{
    "key": "action_opportunity_find",
    "type": "action",
    "name": "opportunity:find",
    "display_name": null,
    "parameters": {
        "pipeline": {
            "name": "Sales"
        }
    }
}

Validation and runtime caveats

The node runs only after its Automation is explicitly reviewed, published, and active.

See the Automation JSON import format for the envelope, dependency resolution, graph rules, complete examples, and AI author checklist.