Flow reference: Bottly Storage
Find Record
Find the newest record where a field equals a value.
Find the newest record where a field equals a value.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Table — table
Name the bot-owned record collection consistently, such as tickets. A typo addresses a different table, not an alias of the old one.
Input: Text.
Default:
records.Field — field
The stored field name to compare. Match the name used when creating the record.
Input: Text.
Default:
user.Equals — value
The value to store, compare or process. Use the required type and a variable only after the source block has run.
Input: Text with variable suggestions.
Default:
{user.id}.Store as — storeAs
Choose a short result prefix such as result. Later blocks must use this same prefix and run after this block. It is not a Discord channel or a persistent table.
Input: Text.
Editor guidance: Read fields as {record.fieldName}
Default:
record.Outputs and next steps
found: A matching record exists.missing: No matching record exists; handle first use.Read the result after this block, using its configured prefix and the fields supported by the selected operation. Do not assume every response has a text or id field.
Test and troubleshoot
Test a missing record, then save and read the same lookup value. Use a narrow filter for Update/Delete. Renaming a table or field changes where the lookup runs.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).