Loop issue and REST API trigger issue
After upgrading to 2.0, most of the things were going well until I tried to migrate most of the things from Zapier or other platforms like that that to BuildShip.
Below are the two biggest challenges I faced:
1. Loop
- Loop node is not consistent. I have a list of 300 contacts
- I tried to loop each one of the contacts and send an email to them via SendGrid
- I have 3 nodes (airtable retrieval node, branch node, SendGrid node) in a loop
- Only the first node in the loop is triggered (Get a Record in Airtable, the retrieval node)
- The rest of the nodes did not get triggered at all
- My setting for the concurrent rate is "1"
2. REST API trigger
- Due to the loop issue, I opted for an alternative solution
- have only 1 node within the loop, which is to send an HTTP request to trigger another workflow (send one email via SendGrid, on one Airtable record, one at a time), lets call it "SendGrid Workflow"
- While the HTTP request was triggered successfully 300 times, most of them failed to trigger the "SendGrid Workflow" to send the emails out
- the success rate of triggering the "SendGrid Workflow" was 30 out of 300, 10%, 90% failed
I got very frustrated as I am not using this to send marketing email, rather, I am send email for important date reminders and etc. Without consistency, cannot reply upon it.
I got the workaround, which is to use a platform like Zapier to send each record from Airtable to trigger "SendGrid Workflow" with a 2 seconds interval in between each request. This worked well with 100% success rate.
I hope someone can help me rectify this without me having to go through another platform to do so. Thanks.
Below are the two biggest challenges I faced:
1. Loop
- Loop node is not consistent. I have a list of 300 contacts
- I tried to loop each one of the contacts and send an email to them via SendGrid
- I have 3 nodes (airtable retrieval node, branch node, SendGrid node) in a loop
- Only the first node in the loop is triggered (Get a Record in Airtable, the retrieval node)
- The rest of the nodes did not get triggered at all
- My setting for the concurrent rate is "1"
2. REST API trigger
- Due to the loop issue, I opted for an alternative solution
- have only 1 node within the loop, which is to send an HTTP request to trigger another workflow (send one email via SendGrid, on one Airtable record, one at a time), lets call it "SendGrid Workflow"
- While the HTTP request was triggered successfully 300 times, most of them failed to trigger the "SendGrid Workflow" to send the emails out
- the success rate of triggering the "SendGrid Workflow" was 30 out of 300, 10%, 90% failed
I got very frustrated as I am not using this to send marketing email, rather, I am send email for important date reminders and etc. Without consistency, cannot reply upon it.
I got the workaround, which is to use a platform like Zapier to send each record from Airtable to trigger "SendGrid Workflow" with a 2 seconds interval in between each request. This worked well with 100% success rate.
I hope someone can help me rectify this without me having to go through another platform to do so. Thanks.
