Dylan Sather (Pipedream) : Hi , data is scoped to a single invocation of a workflow. When your workflow is triggered, it runs with the data you send to it (via HTTP request, for example), and that triggers an invocation with that data. If you trigger the workflow with different data, a separate invocation runs, completely independent of the first. So there’s no collision between the data.
Dylan Sather (Pipedream) : Is there a way for you to pull the orders from an API on your end when the workflow runs? For example:
You schedule the email to run by sending an HTTP request to your task scheduler, with the user ID / email of the user, telling it to schedule the event for 24 hours later.
When the event is scheduled, it triggers your workflow with the user ID / email you passed in step 1. Within the workflow, you could fetch the current order data and format the text of the email.
This way, the order information isn’t embedded in the scheduled event, and can be fetched only when you’re ready to send the email. Would that work?
Dylan Sather (Pipedream) : When you add a new step to your workflow, you should see an option to add the HTTP / Webhook Request action. That allows you to make any HTTP request in a workflow. It’ll return the data from the API as “step exports” that you can use in future step (you’ll see the return data below the step when you run your workflow). Let me know if that helps
Dylan Sather (Pipedream) : Take a look at Settings | Env - Pipedream . Pipedream supports environment variables, which lets you store any API key securely and they access it your workflow using process.env.YOUR_API_KEY. See the docs for more info on how that works.