So we were thinking we can use Pipedream workflow to create a sort of email automation series, kind of like a drip campaign. We were wondering if we were thinking about this correctly, if it’s possible and what we might be missing. Our idea is that if someone buys a particular product on the website, we execute a webhook call to Pipedream workflow and send in the buyer information. Then we would have a Workflow delay as the next step in the workflow, say delay the workflow for 7 days. After the delay, we would send an email to the customer and then delay another 7 days. Then we would send one final email to the customer and end the workflow. Would something like this work? What happens as more emails come into the workflow, will different workflows be able to stayed delayed for different times, so they will be in different “state” so to speak? Is there a liimit to the amount of executions of a workflow that can be delayed at one time? I mean, let’s say we had 1,000 customers in the workflow at one time, with each at a different step?
Definitely yes, we have this exact workflow internally when new users sign up for Pipedream – you can check it out here: New user email drip campaign
And check out our docs on concurrency and throttling controls – you’ll need to manage the queue size, since suspended executions all go in to your queue: Concurrency and Throttling - Pipedream
Here’s where it is in your workflow’s settings:
Thanks. So we would leave the concurrency as 1, but increase the queue size to the amount of customers we think could be in the workflow at one time, including the delayed ones?
Yep, Pipedream can handle your email automation plan. You can trigger it with a webhook, set delays for emails, and manage different workflows for each customer. Just confirm with Pipedream about any execution limits for handling a large number of customers at once.