Skip to main content

Get Lark Base record details

Sophie avatar
Written by Sophie
Updated yesterday

Definition and Usage

Retrieve detailed information for a specified Lark Base record using its record ID. You can locate the target table either by its name or by its unique ID, then fetch the record’s fields and values for downstream use in your workflow.

Parameter Values

Input Parameters

Parameter Name

Description

Possible Values

Required

Options / Notes

Lark Base

Select the connected Lark Base object to operate on.

Connected Lark Base object

Yes

Obtain this from a prior “Connect Lark Base” step; ensure the connection is valid.

Locating mode

Choose how to specify the table.

By name, By ID

Yes

Use By ID for reliability when names change; use By name for readability.

Data table name

The table name to read the record from.

Any valid table name

Conditionally

Required if Locating mode = By name; ensure exact spelling and case.

Data table ID

The table ID to read the record from.

Any valid table ID

Conditionally

Required if Locating mode = By ID; prefer this in automated or multi-environment setups.

Record ID

The unique ID of the record to retrieve.

Any valid record ID

Yes

Must exist in the specified table; confirm you’re using the correct environment/base.

Advanced Settings

No advanced settings available.

Error Handling

Parameter Name

Description

Throw error & stop

When an error occurs, the action will stop execution.

Retry command

The action retries the command if an error occurs.

Ignore error & continue

The action ignores the error and continues workflow execution.

Variables Produced

This action outputs a variable containing the retrieved record’s data for later steps. Use it to reference the record’s fields and values in subsequent actions, pass it to transformations, or compare it with other records. It is structured so you can access field-value pairs directly in the workflow.

Using Variables in Conditions

You can pass dynamic values from earlier steps into this command. For example, provide the table name, table ID, or record ID from variables populated by previous actions. If the UI shows a {x} indicator next to a field, that field accepts variables. Use this to build flexible workflows that adapt to different tables or records at runtime.

Notes

  • Ensure you have already connected to Lark Base in the same workflow before using this command.

  • Choose one locating method: if you pick By name, provide Data table name; if you pick By ID, provide Data table ID.

  • Record ID must belong to the specified table; mismatches will cause retrieval failures.

  • Table names can be duplicated across bases or spaces; prefer table ID to avoid ambiguity.

  • Consider handling errors for missing/renamed tables or deleted records, especially in shared environments.

Did this answer your question?