Using zapier webhooks to make HTTP requests to the Memberstack API Answered

• 

  Duncan from Memberstack

  • September 14, 2023 07:39

  Josh Lopez What do you think? I assume the answer is yes… but I have not done it before.

  Felipe Izquierdo what are you hoping to do with the Admin package? I might know of an easier way to accomplish your goals 🤞

  0
• 

  Felipe Izquierdo

  • September 14, 2023 07:39

  My users have a custom field called 'student-class', every week I want to bulk update the metadata of all the members who are in the same class, with their corresponding 'class video' (metadata).

  So for example, I'd like to find all the members whose 'student-class' is 111, and then bulk update those members metadata to the corresponding video for class 111 (which I have in a zapier table).

  I currently have a trigger when the zapier table is updated, next I'd like to use the make a request to memberstack to find and bulk update the corresponding members.

  0
• 

  Josh Lopez

  • September 14, 2023 07:40

  Hey Felipe Izquierdo the zapier app and the Admin Package should be similar. Both are not made to update members in bulk. What is in the Admin Package that is not in the zapier app that you need?

  0
• 

  Felipe Izquierdo

  • September 14, 2023 07:41

  In Zapier I have to first find the member by their ID and then I can update that member. Using the Admin Package I was going to do something like this https://docs.memberstack.com/hc/en-us/articles/12962278175899--Code-Bulk-Update-Members, essentially run an update loop through all the members and based on which class (custom field) they are in update their meta-data to the respective latest class video url.

  In theory if in Zapier I could find members by their custom fields or other things than the memberstackID then I could update each member that is found with class = 111 (custom field) one by one using a Zapier loop. But I think the reason I need the admin package is essentially to be able to list all members or to search for them in a smarter way to bulk update them (as in the article above).

  0
• 

  Duncan from Memberstack

  • September 14, 2023 07:41

  Felipe Izquierdo another idea… what if the “metadata” lives on your website and it only gets added to the member or displayed when they log-in AND are in class 111? That way you don’t have to bulk update the members? They can “update themselves” when they visit a page or perform an action.

  not sure if I’m thinking of that correctly, but might give you some ideas

  0
• 

  Felipe Izquierdo

  • September 14, 2023 07:42

  I didn't think I could do that since it's sensitive information, but I just realized I could use your Hosted Content feature and make it available to all members. Question: is there a way to access Gated/Hosted Content via the $memberstackDom, with javascript in webflow? I need to have a few different hosted contents and display those based on the current member custom field (student class number). Essentially I need my own custom logic for if to display which of the hosted content for each member.

  cc Josh Lopez

  0
• 

  Duncan from Memberstack

  • September 14, 2023 07:43

  That’s a great question 🤔 I don’t think it’s accessible in that way. Memberstack delete gated content from the page on load, so I think you’d run into some dead-ends.

  What do you think about using free-plans to gate access to content instead of custom fields? Then you can rely on Member’s built in content gating features

  0
• 

  Celvin Klassen

  • January 09, 2024 00:18

  Zapier provides a way to make HTTP requests through webhooks, and it can be used to interact with APIs, including the Memberstack API. While the Memberstack documentation mentions the use of npm or yarn for Node.js packages, you can indeed leverage Zapier's webhooks to make HTTP requests without the need for your own backend or coding.

  Here's a general guide on how you might set this up in Zapier:

  1. Create a Zap:

     • Log in to your Zapier account and create a new Zap.

  2. Set Up Trigger:

     • Select the appropriate trigger app for your workflow. This could be an event in another app that initiates the Zap.

  3. Add Webhooks by Zapier as an Action:

     • Add a step to your Zap and choose "Webhooks by Zapier" as the action app.

  4. Choose a Webhooks Action Event:

     • Select the specific action event, such as "Custom Request" or "Catch Hook," depending on your workflow.

  5. Configure Webhooks Action:

     • Set up the webhook with the details required by Memberstack's API. This includes the URL, method (GET, POST, etc.), headers, and data payload.

  6. Test Webhooks Action:

     • Perform a test to ensure that the webhook is successfully making requests to the Memberstack API. Check for any errors or issues in the Zapier task history.

  7. Set Up Additional Actions (Optional):

     • Depending on your workflow, you can add more actions to your Zap to handle the data returned by the Memberstack API or perform subsequent tasks.

  8. Enable the Zap:

     • Once you are satisfied with the configuration, turn on your Zap to start the automation.
  1

Please sign in to leave a comment.