Skip to main content

Get Lark access token

Sophie avatar
Written by Sophie
Updated yesterday

Definition and Usage

Use this action to obtain a Lark access token using either an existing or a custom Lark app. The token enables authenticated automation with Lark services. Provide the app’s credentials from the Lark Developer Console, then store the resulting token for later steps in your workflow.

Parameter Values

Input Parameters

Parameter Name

Description

Possible Values

Required

Options / Notes

App ID

Unique identifier of the Lark app.

Any valid Lark App ID

Yes

Find it in Lark Developer Console > Credentials & Basic Info; ensure it matches the intended environment (e.g., global/China).

App Secret

Secret key for the Lark app.

Any valid Lark App Secret

Yes

Keep it confidential; rotate if compromised; ensure it corresponds to the provided App ID.

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 produces a variable that holds the retrieved Lark access token. Use this token in subsequent Lark-related actions to authenticate API calls or operations within the same workflow.

Using Variables in Conditions

You can pass dynamic values from earlier steps into this command’s fields if your workflow supports variables. In many builders, fields marked with {x} indicate variable support. Store the token in a variable, then reference that variable in later steps that require authentication, conditions, or headers.

Notes

  • Ensure the Lark app is created and the App ID and App Secret are active in the Lark Developer Console.

  • The App Secret must match the App ID; mismatches will fail authentication.

  • Network or permission issues in the Lark Developer Console can prevent token retrieval; verify app permissions and tenant access as needed.

  • Store the token securely and reuse it for subsequent Lark actions within its validity period; refresh by rerunning this action when it expires.

Did this answer your question?