Update Airtable record from a Shared View using n8n

​@Kazuonio 

Your #1 best bet for this is to use Fillout’s advanced forms for Airtable.

Fillout is 100% free and it allows you to update Airtable records using a form.

I demonstrate this on this Airtable podcast episode:

• Using Fillout to update an existing Airtable record & create an eSignature approval process with PDF file creation.

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Definitely agree with ​@ScottWorld that Fillout is the best and simplest solution for your use case.

From an n8n/make perspective, I bet you could figure out something utilizing webhooks if you really wanted to (especially if the state change is always 1 step forward) but unless you have devs on staff that want to get nitty gritty, Fillout is sitting there ready to go haha.

Unfortunately there is no field-level edit permissions on Shared Views, they are read-only by design.  Seems you have the right idea with n8n.  Best way to do it is to use an Interface form or any other form with the record ID passed as a URL parameter and adding a single-select dropdown that pulls your predefined status values.  The agency clicks a link, chooses a status. Then submits either an n8n or an Airtable automation updates just that single field.  This will keep the base fully locked down because they will never touch Airtable directly.  You will need an external form/link because buttons in Shared Views cannot trigger automations for non-collaborators.

​@Kazuonio 

Since read-only records in Airtable can still contain clickable links & clickable buttons, you can do this with webhooks as well.

As ​@DisraeliGears01 mentioned above, if you’d like to use the webhook method of doing this, I prefer using Make over N8N.

Here is the link to Make’s custom webhooks & custom webhook reponses.

I show how to use the Make webhook method on this Airtable podcast episode.

And if you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread,

Hope this helps!

If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

Hm, by ‘shared view’, do you mean Interface?  If not, I’d recommend looking into using an Interface and inviting them as a read-only interface collaborator instead; easier to use than a shared view with a password

I’d say just use Fillout for this, really; would be much simpler than using n8n and cheaper than Interfaces/Portals even if you go past their free tier of 1k submissions per month

Hi everyone,
Thanks again for all your suggestions!

After looking into the different options, I decided not to use Fillout because we prefer not to give another third-party provider access to our Airtable data and wanted to keep everything within our existing stack.

Instead, I built a small n8n workflow. A link in our password-protected Airtable shared view opens a custom HTML page via a webhook. The page displays the task and current status, lets the external agency update the status using checkboxes, and then a second webhook updates only the “Status Massnahme” field in Airtable before redirecting the user back to the shared view.

This gives the agency a simple interface while keeping the Airtable base read-only, with all updates handled through n8n.

So far, it has been working really well for our use case. Thanks again for pointing me in the right direction!

​@Kazuonio  That's a really clean solution, keeping the custom HTML page as the intermediary means the agency gets a purpose-built UI and your base stays fully locked down. 😎 Good call on skipping Fillout if third-party data access was a concern. Love it when people come back and share their solutions on the thread to close the loop. 

Holly @Simple Stack

​@Kazuonio you neither need Fillout nor n8n for this. You can accomplish this entirely within Airtable.

1. Move off Shared Views, use an Interface instead

A Shared View is all-or-nothing: read-only or editable, no in-between control over which fields. An Interface lets you show only the fields you want, and add a button that does something specific, without exposing the base or giving edit access to records directly.

2. Create a "Status Updates" table

Two fields:

• Record ID (single line text) — the ID of the record to update in your main table
• Status (single select, same options as Status Massnahme)

3. Create a Form view on "Status Updates"

This is what the agency actually fills out. Grab the form's share link from the Share form button, it looks like https://airtable.com/shrXXXXXXXXXXXXXX/formYYYYYYYYYYYYYY.

4. Add a "Status Update Link" formula field in your main table

"https://airtable.com/shrXXXXXXXXXXXXXX/formYYYYYYYYYYYYYY?prefill_Record%20ID=" & RECORD_ID() & "&hide_Record%20ID=true"

RECORD_ID() pulls the current record's ID automatically. hide_Record%20ID=true hides that field on the form so the agency only sees the Status dropdown, not a raw ID box. If your field is named Record ID with a space, it needs to be %20 in the URL. Rename it to RecordID (no space) if you want to skip that.

5. Automation to write the status back

This is the piece that closes the loop:

• Trigger: When a record is created in "Status Updates"
• Action: Update record in [main table] where Record ID equals {Record ID} from the trigger record - set Status Massnahme on the found record to {Status} from the trigger record

6. Button in the Interface

Add a Button element to the record detail layout, action "Open URL," pointed at the Status Update Link field. Agency clicks it, form opens prefilled, they pick a status, submit. Done.