const record = await pd.makeProxyRequest(
      {
        searchParams: {
          account_id: airtableAccount.account_id,
          external_user_id: externalUserId,
        },
      },
      {
        url: `https://api.airtable.com/v0/${selected_base}/${selected_table}/${recordId}?returnFieldsByFieldId=true`,
        options: {
          method: "GET",
        },
      },
    );

works as expected

const record = await pd.makeProxyRequest(
{
searchParams: {
account_id: airtableAccount.account_id,
external_user_id: externalUserId,
},
},
{
url: https://api.airtable.com/v0/${selected_base}/${selected_table}/${recordId}?returnFieldsByFieldId=true,
options: {
method: "GET",
},
},
);

works as expected

Hi @MartinMalinda
It helped to locate the problem.

returnFieldsByFieldId option defined in get-record-or-create actions wasn't being forwarded to the Airtable API.

Also
The getRecord method in commonActions was calling .find(recordId) from the Airtable SDK without passing any flags further.
However, exploring the Airtable repo I found out .find() does not support additional options like returnFieldsByFieldId.
In contrast, methods like .update() do accept an opts parameter.

I updated getRecord to use a direct API request with params: { returnFieldsByFieldId: true } instead of relying on .find().

Also added returnFieldsByFieldId to get-record.mjs

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/BUG-returnFieldsByFieldId-prop-not-used-in-airtable_oauth-get-record-or-create-1e6bf548bb5e81128b81ddb29242f8b3