How to save multi-step form progress in Memberstack when using Airtable as a database? Answered

Post author
Gaurang Vasava

Hi everyone,

I'm currently working on a web app where all data is stored in Airtable. The app includes a multi-step form with 4 steps for users to add item details.

I’m trying to implement a feature where a user's progress is saved as they go through the form. For example, if a user starts adding details for "item-x" and reaches step 2, but then closes the form or doesn’t complete it, I want to save their progress. Later, when they return, I want to show "item-x" with a status of "draft" and allow them to continue from the step where they left off.

Does anyone have experience with this kind of functionality in Memberstack? Any advice or guidance on how to best approach this would be greatly appreciated!

Thanks in advance!

Comments

2 comments

  • Comment author
    Memberstack Team
    • Official comment

    One approach you might find useful is to adapt Script #197 – Multi-step Form Submission Handling. It’s designed to save data at each stage of a multi-step form, so instead of only committing values at the final submit, you can push partial progress into Airtable after each step. That way, if a user stops at step 2, you’ll already have “item-x” stored with a status like draft, and when they return you can query Airtable to reload their last saved step and continue the flow.

    That said, if your main requirement is deep Airtable integration (like resuming drafts and syncing status fields), you may need to pair #197 with a custom API call or automation tool (e.g., Make/Zapier) to handle the “save after each step” logic. Script #197 is best when you want progress tracking and validation inside Memberstack, while Airtable handles the persistence and draft management.

  • Comment author
    A J

    Hey Gaurang Vasava, I can see that the easiest way to do this would be to have each step of the form in separate pages and have each form as profile update forms which you can connect to Memberstack. From a user's pov, it will just seem like one form with multiple steps, but in the back-end, what you essentially will be doing is once the user fills step 1 and proceeds, the data will be stored in memberstack custom fields (if you have custom fields setup for the form in MS). So even if the user closes the form on step 2, the step 1 and 2 data will be stored in Memberstack and when they come back to the form they can see all the details pre-filled (which they can also edit if they want).

    To give you a starter template, check this onboarding template out and see how it is setup, you can also check this guide which explains how the multi-page multi-step form works.

    Hope this helps.

    Now in case you have taken the slider approach for multi-step form, you can try to replace the Next button with a form submit button and see if you can configure it to work in a way that it submits the data to memberstack and also reveals the next step of the form.

    0

Please sign in to leave a comment.