Hello friends, how are you?!
I created a flow with the objective of updating the labels of my contacts on my Whatsapp Business from a Google Sheets spreadsheet.
Customers who were served less than 30 days ago receive the ACTIVE customer label, while customers who were served more than 30 days ago receive the INACTIVE customer label.
My initial idea would be to first consult the Z-API to return my Whatsapp Business contacts. I would then consult a Google Sheets spreadsheet that contains my clients’ information (including the date of the last consultation), and then update the labels.
So, I made this first flow below with this idea. However, the number of contacts on Whatsapp is very large and consequently the number of requests ended up blocking n8n.
In an attempt to reduce the number of requests, I did the opposite, I started by consulting the clients’ spreadsheet on Google Sheets. Next, using my clients’ phone number, I consult the Z-API to check if this contact is among my Whatsapp Business contacts and then I update the labels for this contact!
However, unfortunately, the number of requests is still large and n8n keeps crashing.
I ask: How can I further clean up my flow to minimize this crash?
Thinking about solving this problem, I created a column in the spreadsheet to update the date of the last synchronization. With that, I thought about creating a support flow to search for n8n Executions, evaluate the latest Failed executions and, with that, trigger a new flow trigger to update only the contacts that have not yet been synchronized.
Would this be the best solution? Would you have any other suggestions on how to resolve this problem?
Thank you in advance!
- n8n version: 1.22.6
- Database (default: SQLite): SQLite
- n8n EXECUTIONS_PROCESS setting (default: own, main): Main
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: MacOS