Skip to main content
Question

Update Airtable record from a Shared View using n8n

  • July 6, 2026
  • 2 replies
  • 18 views

Forum|alt.badge.img

Hi everyone,

I'm looking for the best approach for the following use case.

We have a read-only Shared View that we share with an external agency. They should be able to update only one field (Status Massnahme), which contains multiple predefined single-select status values.

We do not want to give them collaborator access or edit permissions to the base.

My initial idea was to include a button or link in the Shared View that would trigger an n8n workflow to update the record. However, since there are many possible status values, I'm wondering if there's a better approach.

Has anyone implemented a similar workflow?

Some questions:

  • Is it possible to let external users update only one field from a Shared View?

  • Would you recommend n8n, Airtable Portals, Fillout, Interfaces, or another solution?

  • If using n8n, how would you pass the record ID and let the user choose from multiple status values?

  • Are there any limitations with buttons or links in Shared Views that I should be aware of?

The goal is to keep the Shared View read-only while allowing the agency to update only the campaign status in a secure and simple way.

Thanks in advance for any recommendations or examples!

2 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • July 6, 2026

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:

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


DisraeliGears01
Forum|alt.badge.img+22

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.