Cannot map "URL Param" to Airtable "Linked Record" field in List Block Action (Custom Workflow)

Hi community, I’m stuck with a specific issue in a List Block action button using a Custom Workflow.

The Setup:

  1. I have an Airtable Base with 3 tables: Products, Leads, and a junction table Quotes (Richieste Preventivo).

  2. The Quotes table has a field called Lead which is a Link to another record (linked to the Leads table).

  3. On Softr, I have a List Block connected to Products.

  4. The page URL contains the Lead ID: https://myapp.softr.app/results?recordId=recXXXXXXXX

The Goal: I want to create a button “Request Quote” on the Product Card. When clicked, it should run a workflow: Airtable > Create Record in the Quotes table. It needs to map:

  • Product: Current Record ID (This works).

  • Lead: The URL Param (recordId) from the browser.

The Issue: In the Workflow editor, when I try to map the value for the Lead field (which is a Linked Record type), the dropdown does not show “URL Param” or any global variables.

  • I tried searching for “url”, “param”, “recordId”, “query” inside the dropdown, but it returns “No options”.

  • It seems the dropdown is strictly filtering for “Records” and hiding the Global Variables options.

  • I cannot force-paste the variable {url_param:recordId} because the UI resets the field.

Screenshots attached:

  1. My Workflow setup.

  2. The dropdown menu being empty when searching for the parameter.

Has anyone faced this? Is there a way to force the input to accept a text string (the ID) or a URL Param for a Linked Record field?

Thanks!

Would creating an API Call button in Softr going to an Airtable Webhook work for you?

I wanted to avoid API calls when looking at the AIRTABLE integration. Do you recommend using the integration?

I’m no expert, but found in some instances Webhooks are the only way forward… and whilst API can sound scary for no-coders, it’s actually quite easy between Softr and Airtable. Let me know if you get stuck, but Grok or whatever will likely help you. One quirk of setting up the webhook as a trigger in Airtable (which generates for you a unique URL in Airtable as the hook) is that before the hook “activates” you need to ping it from Softr… Airtable will initially tell you on testing it isn’t working. But if you add the Airtable webhook URL into Softr’s API button, click the API button, it will then “ping” Airtable. Then test the webhook in Airtable, and hopefully Airtable will then tell you the webhook is being received. You may know this already, in which case ignore me! That’s only if you actually need an API button. It’s just my hunch from what you described.