> ## Documentation Index
> Fetch the complete documentation index at: https://flywheel.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Find Event

> Search for specific events related to the current user to gather additional context

<iframe src="https://app.flywheel.cx/doc-comp-previews/workflow-node-preview?type=find_event" title="Workflow Node Preview" width="100%" height="250px" className="border dark:border-[#1C1C20]  rounded-xl" />

## How Find Event Works

Search for specific events related to the current user to gather additional context for your workflow. This action looks through the user's event history to find relevant events that can inform subsequent actions.

## Configuration

<Columns cols={2}>
  <Card title="Inputs">
    <ParamField path="Event Name" type="string" required>
      The name of the event type to search for. Examples: `purchase_completed`, `feature_used`, `page_viewed`.
    </ParamField>
  </Card>

  <Card>
    <iframe src="https://app.flywheel.cx/doc-comp-previews/workflow-config-preview?type=find_event" title="Workflow Config Preview" width="100%" height="400px" className="" />
  </Card>
</Columns>

<Card title="Outputs">
  <ParamField path="event" type="object" required>
    The found event data that matches the search criteria.

    <Expandable title="Event Properties">
      <ParamField path="event.event_name" type="string" required>
        The name of the found event.
      </ParamField>
    </Expandable>
  </ParamField>
</Card>

## Use Cases

**Behavior Analysis**

```
Event Name: purchase_completed
Query Conditions: purchase_amount > 100
Selection Strategy: newest
Use: Personalize recommendations based on recent high-value purchases
```

**Feature Usage Tracking**

```
Event Name: feature_used
Query Conditions: feature_name = "analytics_dashboard"
Selection Strategy: oldest
Use: Send advanced analytics tips based on first usage
```

**Onboarding Progress**

```
Event Name: tutorial_completed
Query Conditions: tutorial_step = "setup_complete"
Selection Strategy: newest
Use: Skip basic setup in welcome email sequence
```

**Support Context**

```
Event Name: error_occurred
Query Conditions: error_type = "payment_failed"
Selection Strategy: newest
Use: Provide targeted support based on recent error events
```

## Best Practices

**Efficient Event Queries**

* Use specific event names to reduce search scope
* Apply appropriate query conditions to filter results
* Consider the performance impact of broad searches

**Context Utilization**

* Use found event data to personalize subsequent actions
* Consider what happens when no matching events are found
* Combine multiple Find Event actions for complex analysis

**Data Management**

* Be mindful of data retention policies
* Use appropriate selection strategies based on use case
* Monitor query performance and adjust conditions as needed
