![]() Zapier doesn’t have a “trigger” for Airtable updates (just new records) and the API (as you know) doesn’t expose date modified (only date created). I know this isn’t the answer you were looking for, but this is what it is.To the best of my knowledge, NOTHING can track changes/updates to records other than Airtable itself. Zapier / Make responds to Webflow’s backend server with a success / fail message.Zapier / Make receive that Webhook call.Webflow sends that info to the Webhook destination that you setup.Webflow triggers a Webhook (if you’ve set it up).Webflow responds to the form submit with a success / fail message.The user submits a memberships signup form.The problem is that you’ve broken the connection between the users web browser and the success / fail response. So capture when a new membership is created and send that to Zapier / Make (Integromat) to do your Airtable lookup. If you didn’t already try this, a Webhook is a fun little no code thing that allows you to capture events and send them to any destination you choose (much like the forms action field). You could use the Webflow Webhook Creator tool to create a Webhook. The memberships_user_account_created or memberships_user_account_updated webhook events. This is the easiest to build, involves no custom code, and will work correctly with Webflow’s onboarding process and ecom memberships as well. In this scenario, I can sign up with an ID of askdjfwekfj, and Webflow will still create an account- however I won’t have access to anything I shouldn’t. Gate all of your content to those access groups.On new account creation events, have Zapier verify that ID and then assign appropriate access groups to that user.Add that field to the Sign Up page form, as a required field.Add a custom MyMemberID user data field to your memberships.The most compatible way should to to leverage the self-enrollment flow I’d stay aligned with that to keep things simple. Both can work here but either way, the /sign-up page is central to onboarding. You have two possible approaches on sign-up, which is self-enrollment at /sign-up or, invitation via the API. I’m guessing this requires custom code with an event listener (show sign-up form, IF membership-id-form is successful), but I only want the membership-id-form to be successful if we can verify we have a record of what the user inputted. I do not want users to be able to create a user account if we can’t verify a specific field is associated with them in our Airtable database. I’ve managed to set up a zap where the form submission was validated in Airtable with “Find Records” and it found my 6-digit number I entered in my Webflow form, but I’m stuck on how to get Airtable to confirm back to Webflow that “Yes! This 6-digit number does exist in Airtable, the user may proceed in creating an account”. ![]() ![]() ![]() When the form is submitted and the 6-digit number the user entered is NOT in my Airtable database record, the form needs to say “Sorry we couldn’t find your member ID in our records” (or something like that). When a user puts in their member ID, I want the form to only show a success status IF the 6-digit number is found in my Airtable database record. On the new native memberships Sign Up page, I have a custom field form asking for a 6-digit member ID (a member ID completely unrelated to Webflow memberships). I’ve been researching different ways how to accomplish this, looking into Make/Zapier, and custom code, but my custom code knowledge is more limited.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |