# Find lookup table row

Source: https://neondeerdata.com/docs/platform/automations/steps/find-lookup-table-row/

Step · Lookup and record data

Finds one row in a Neon Deer lookup table whose lookup field matches a value, and outputs its shared fields.

## Inputs

| Label   | Key                    | Type                   | Required | Notes                                                                                                                                                                                   |
| ------- | ---------------------- | ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Table   | `table_id`             | Table                  | Yes      | Searchable list of tables that have at least one lookup field. Variables cannot be wired.                                                                                               |
| Find by | `lookup_definition_id` | Lookup field           | Yes      | The table’s lookup fields. A member field appears twice: by member, and as “\<label> ID” to match an ID typed as text. Variables cannot be wired.                                       |
| (value) | `lookup_<type>`        | Matches the field type | Yes      | One input in the field’s type: text, URL, number, yes/no checkbox, date, timestamp, email, domain, workspace member (or member ID as text), or record (after choosing a Record object). |

## Outputs

| Label                  | Key           | Type       | Always set | Notes                                                                                                                                                                                               |
| ---------------------- | ------------- | ---------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Found                  | `found`       | True/false | Yes        |                                                                                                                                                                                                     |
| (one per shared field) | `<field key>` | Field type | No         | One output for each field shared with workflows, keyed by the field key. Absent when the row has no value; 0, false and empty text are kept. Member fields output an actor; record fields a record. |

## How it behaves

- Reads the table’s current fields and lookup fields from Neon Deer, checks the value, then asks Neon Deer for the row whose lookup value equals it.
- Values are checked strictly, with no conversion: text up to 1,000 characters, a finite number (whole numbers within ±9,007,199,254,740,991), a real `YYYY-MM-DD` date, an ISO timestamp with an offset, a member UUID. A record is resolved to its object and record IDs.
- Matching rules (case, trimming, time zones) are applied by Neon Deer; see the Lookup tables guide.
- No matching row is a normal result: Found is false and no field outputs are set. Branch on Found.
- Never falls back to another lookup field if the selected one was removed.
- When the Neon Deer connection exists and a table and lookup field are chosen, each run sends a value-free activity event to Neon Deer (table, lookup field, result, duration, workflow IDs). One attempt, 2-second limit; a failed send does not change the step’s result.

## Limits and constraints

- Each request to Neon Deer times out after 5 seconds.
- For record values, the step lists Attio’s objects once per run and gives up after 5 seconds.
- The table picker shows the first 50 matches for a search.

## Errors

Fails when

- Rate limits, timeouts, temporary unavailability and a table that changed mid-run are retryable; configuration and connection errors are not.

For errors that every step can return, see [Troubleshooting](https://neondeerdata.com/docs/platform/automations/troubleshooting/).

## Example

Route a new company to its territory owner using the company's country code.

**Example inputs**

| Input        | Value        |
| ------------ | ------------ |
| Table        | Territories  |
| Find by      | Country code |
| Country code | DE           |

**Example outputs**

| Output | Value                         |
| ------ | ----------------------------- |
| Found  | true                          |
| Region | EMEA                          |
| Owner  | Priya Shah (workspace member) |

Region and Owner are output because both fields are shared with workflows in Neon Deer; a field that is not shared produces no output. Needs a Neon Deer plan that includes lookup tables. With no matching row, Found is false and no field outputs are set.