Mohammed Zeeshan : Let me know if the link is accessible.
Dylan Sather (Pipedream) : got it, thanks. I modified the code slightly and ran a couple of test events through the workflow. Take a look at the last event - it appears to have succeeded, but I want to make sure it looks OK in Memberstack
Mohammed Zeeshan : Awesome, let me go through that and will let you
Mohammed Zeeshan : It ran without any errors but doesn’t update the field specified inside body {}
Mohammed Zeeshan : I think anything specified inside body is silently rejected. I just tried updating the email field which is already created. and no changes.
Mohammed Zeeshan : Are we missing to add method: 'POST' to that step? or is it declared implicitly ?
Dylan Sather (Pipedream) : right, the step Tod shared defaults to “GET”, so you can add a method: "POST" to that code and make any other necessary changes to map code in the other step to this new one
Mohammed Zeeshan : Great! i updated the code and still it returns same object. Interesting!
Dylan Sather (Pipedream) : do you not see the update in Memberstack?
Mohammed Zeeshan : No, no updates in Memberstack. But it works without any errors now.
Mohammed Zeeshan : Update: It worked finally and updated Memberstack. Memberstack uses data instead of body
Mohammed Zeeshan : OMG! so glad to see it updates :pipe: Thanks @UN1BV42B1 for your generous support so far. There are still some steps to accomplish and will see how it goes.
Next up, creating user dashboards in Webflow
Dylan Sather (Pipedream) : that’s great, glad that’s working
Mohammed Zeeshan : Hey 
I have one question
> TL;DR : Question about having 2 triggers runs on the same workflow
> 1st trigger flow is already completed that started from user sign up using Memberstack
> 2nd trigger is Webflow form submission whose values have a dependency on the first trigger
while the user signs up and onboards, a form is submitted inside Webflow asynchronously.
The signup process is already set and works flawlessly in the Pipedream workflow.
Website link for testing the flow
Now can i add next step to be a webflow form submission trigger? technically i don’t see this option in Pipedream.
Conventionally with Zapier we used to start a new workflow starting from Form submission since form submission step is only available as the first step of the workflow.
This is my planned worflow:
This form data along with member-id captured from the previous step (sign-up step) is then formatted and sent back to Webflow as a PUT request to that members collection.
With Zapier i had to store the member-id in an airtable field (acts as db) then retrieve from there whenever needed in future workflows.
Thanks in advance 
Dylan Sather (Pipedream) : Hey Mohammed, just to confirm, it sounds like you want to run your existing logic (workflow triggered by user sign up, you run a couple of steps), and then wait for the user to submit webflow form submission, and process that data - is that right?
Dylan Sather (Pipedream) : like with Zapier, you can only have a trigger at the start of the workflow. Can you can separate the form submission logic into a new workflow, triggered on the form submission? We do have a Webflow Form submission event source, see New Source - Pipedream
Dylan Sather (Pipedream) : that can act as the trigger for a new workflow
Mohammed Zeeshan : Yeah, you understood that correctly. If we perform 2 workflows and need to keep track and store variables between them, does pipedream offers something like environmental variable? Presumably, I’m planning to achieve this using Airtable as a DB but just curious 
Dylan Sather (Pipedream) : we do, but they’re read-only from workflows: https://docs.pipedream.com/environment-variables/#environment-variables
we offer a key-value store, but it’s scoped to a specific workflow: https://docs.pipedream.com/workflows/steps/code/state/
Check out https://kvdb.io/ - easy to use for cases like this
Mohammed Zeeshan : Awesome. Thanks for clarifying 