{logged_in_user:id}

[Lucap6]

Hi all.

I need to call a MAKE webhook. This webhook needs two parameters: the username and the id of the record I am already placed on (the page I am in!).
Online I have found numerous examples that take advantage of {LOGGED_IN_USER:ID} but, while filled in and while correct, the parameter is not being populated (see attachment, for testing purposes I have also try to exposed the ID in this text).

I don’t want use custom blocks.

Is it a bug?

[Lucap6]

This is the example I found online:

[Workflowheroes_Marc]

Hey mate,

“ID” only works if that data is also stored on your data source. I am going to assume you have linked up airtable for this? If yes, go in your airtable and create a column in your user table called : ID (or whatever you want). Turn that into a formula field and have the formula field be : RECORD_ID()

If you need more in depth ideas on how to get a recordID send to a make webhook, have you thought of creating a url within your airtable with the parameters attached, and add an action button in a list details block that activates that link?

Cheers

[Lucap6]

Hi Marc, thankyou for your answer but the structure of the tables is just like that!

The record ID you see in this printscreen is the same, and the correct ID, you can see in my 1st printscreen.

[Workflowheroes_Marc]

change {LOGGED_IN_USER:ID} to {LOGGED_IN_USER:users_RecordID} and see if it works

[Lucap6]

No, it does not solve: the parameter remains fixed and is not replaced with the ID parameter in the URL page.

Also, in the example found online, fixed {LOGGED_IN_USER:ID} is used regardless of the table name and field name on Airtable.

[vikasvimal]

You should expose the logged in user’s record id
And the selected record’s Record ID (you may need to expose record IDs using an Airtable formula in a separate field.)

Also, just putting the {LOGGED_IN_USER:ID} as text wouldn’t work, as you already know.