Action button - Formulating the url of a resource to embed code

So, let’s start the journey to let your users delete a record.

Note that with action buttons coming in the next weeks, this workaround shouldn’t be neccessary anymore

You will need the software Make to perform it. A free version can be sufficient.
My example is about letting my users delete a project. Obviously it can work with any of your use cases.

There are two versions.

  1. Without any correct user experience (the user clicks on it, the record is deleted… outch!)
  2. With a proper user experience (the user clicks on the button, it leads the user to confirmation page

Version 1

First screenshot: a list block with items (projects). I add a button called “delete project”. Each time this button will be pushed, it will automatically delete the project.

Second screenshot: Global overview of the make scenario

Third screenshot: details of the first module of the make scenario

Fourth screenshot: details of the second module of the make scenario

Fifth screenshot: details of the third module of the make scenario

Sixth screenshot: the option “open external url”, within the list block option must be linked to the a field you would create in Airtable.

Seventh screenshot: details of your Airtable settings

Eighth screenshot: details of the formula Webhook

Version 2
This time, when you click on the button “delete project”, the user will be lead to a confirmation page.

Ninth screenshot: Confirmation page look alike.
The block, even if it looks like a CTA block, is in fact a list details block with one title and two buttons, centered. This choice is made because the webhook url has to be called dynamically in your airtable field called “webhook delete”

Just replace the workflow that I described above by linking the “confirm deletion” button to the webhook field in Airtable (same process as above).
After deletion, according to the make scenario (that you don’t have to change even in this version 2), the user will return to the previous page.


I really hope I didn’t forget anything or didn’t make any mistake :sweat_smile:. If you have any problem, you can ask here. Tell me if it works, as this tuto will be pushed to the guides thread of the community


Also, if you wanted to remove without deleting… This is not the right tuto, but ok :joy:

Haha you’re right, I just want them to be able to remove it from their playlist.

To try and make sure I’m being clear about my user case:

A ‘teacher’ explores the ‘resources’ and click an action button to add that resource to their ‘playlist’.

That item then copies itself into their playlist. I then want them to be able to remove that resource from their list.

1 Like

You can use the same workflow, but change the second module of the make scenario. It is currently a delete action.
Change it to an update action.
Each time a teacher favourites a resource, it will update an airtable field of your choice (created or already existing, I can’t know how your Airtable base is set up).

Then set a condtional filter on that list block saying that the field that indicates that the resource is favourited is “not empty” (or anything else that makes sense to you). That way, only not favourited resources will be shown to the teacher.

Just to let you know that you can do this without make, by using Airtable automations (If a record meets condition => Then => update another record (or the same record, depends on how your AIrtable base is set))

I would definitely want to just use Airtable, especially as the action button is soon available.

So how would I co figure this all out? My action button is working to add to a list, but I want them to be able to remove that from their list.

Let your button as it is.
Then in Airtable => automation => when the item is added (which can mean that a record is created or updated, depends on your Airtable setup) => update a record in an other table.
The updated record could belong to a single select field with two choices “favourited” / “Not favourited”.
Then the value of this field will trigger the condtional filter of the list block which where you want the favourited records to be “removed” according to the teacher favourites.

I will try to make a live demo of it, to check if it can properly work.
In the meantime, I suggest you to test Airtable automations, maybe you will find something out.

Will do!

Looking forward to seeing the demo :slight_smile:

I succeeded to do it, that’s not super easy, let me gather everything to post it here.
And at some point you will need make (only if you want your users to unfavourite an item).
No airtable automation possible for this use case, unfortunately.
But note that with coming action buttons feature, this will be much easier to do.

Is it the behaviour you’re looking for?

1 Like

If I click on the last button you see in the video (the broken heart - unfavourite button) it will trigger the make webhook and, according to the conditional filters, the item will disappear from the list block “all your favourited resources” and will re-appear in the list block “available resources”


The only difference would be that I’d want the new list (playlist) to be on the same page as the resources, the resources not to disappear from the main list when ‘added’ or liked. Then when they’re removed from playlist they just disappear from the playlist.

Also, Is there a way of it appearing without refreshing? If not, can there be an ‘auto-refresh’ once you add an item so that it shows up straight away?

And yes, the action button will definitely help a lot!! I just can’t really wait until December or maybe January

Without reloading the page, no.
Except if you use a list details block. Inside of it a checkbox like “unfavourite” => this won"t need a page reload. But the user experience with list details to do so is not really what I would call “a neat experience”…

Ok fair enough! Hopefully the action button will make all of this smoother :slight_smile:

I found a way without make… but with scripting in airtable, inside an automation… :sweat_smile:
let me show you the behaviour with your previous inquiries. Don’t like the global ux for this but it works.
If I were you I would wait a little and play with action buttons

And it would need one more custom code at page level to disable the form “Like” if the resource is already liked
All these workarounds for favouriting/unfavouriting :hot_face::hot_face:

Anyway here is the Airtable automation

1 Like

Wow, thank you so much for the time and effort you’ve put in to this! I think your advice to wait for the action buttons is smart. Hopefully they come this side of Christmas!

Hi Matthieu, How are you? I need to add an action button to my app and, before I go through the process detailed above, just wanted to check in with the Softer team to see if the feature has been added yet.

Hey @JPH,

The team is working hard to launch the option and it is planned to be released by the end of January. :slight_smile: