How do I get the current record ID in Salesforce Flow?

Create a Text variable named recordId and select Available for input . When you launch the Flow from a supported record context, Salesforce sends the current record ID into that variable.

Why is my recordId variable blank in Flow?

The variable may not have Available for input selected, or the API name may not be exactly recordId. Also confirm that users launch the Flow from a record page, record action, or button that passes the parameter.

Can I pass a record ID to an Autolaunched Flow?

Yes. Another Flow, Apex class, Process Builder migration, or supported automation can pass an ID into an Autolaunched Flow. The receiving variable must be a Text variable available for input.

Can a Screen Flow update the record that launched it?

Yes. Use {!recordId} in an Update Records element and select the relevant object. You can then update fields on the current Account, Case, Opportunity, or custom object record.

Can I pass an Account ID and create a related Contact?

Yes. Receive the Account ID in recordId, then use Create Records to create a Contact. Map the Contact’s AccountId field to {!recordId}.

Should I use a quick action or a Flow component?

Use a quick action when users should start the Flow on demand from a button. Use a Flow component when users need the Flow visible on the record page or use it repeatedly while reviewing record details.

How to Pass a Record ID into Salesforce Flow

Imagine a sales representative is viewing an Opportunity and clicks a button to start a Flow. Salesforce should already know which Opportunity the user is working with. The user should not have to search for or select the same Opportunity again.

The same requirement is common in other Salesforce processes. For example, a support agent may open a Case and launch a guided Flow to create follow-up work. In this situation, the Flow needs to know exactly which Case the agent is working on.

This is where passing the current Record ID into a Salesforce Flow becomes useful.

I have used this pattern in multiple Salesforce implementations because it makes Screen Flows much easier for users.

Instead of asking users to manually search for a record, we can pass the current record’s unique Salesforce ID directly to the Flow.

Once the Flow receives the Record ID, it can use that ID to:

Find the related record.
Display record information on a Screen.
Update the current record.
Create related records.
Create follow-up Tasks.
Perform additional business logic.

In this step-by-step Salesforce tutorial, we will learn how to pass the current Record ID into a Screen Flow from a Salesforce record page.

By the end of this tu