Forum Discussion
ArshadKhwaja
8 years agoQrew Commander
Hi Matthew & Harrison, sorry to take you back on this. I re examined the whole thing. All I wantd to do was to lift start and end dates of project completion in my app and create an event in Google calendar. Previously I tried Zapier but it would not work as the primary table had far too many records for Zapier to deal with and the table itself was not visible as it was a parent table to a few children.
In the latest attempt, I created another table and set up two QB actions to add and update records in the child table limiting irecords n terms date range, that is, only report on projects opening next 6 months. I then established a Zap but after a lot of toing and froing with Zapier support, they were supportive though). Turns out that I cannot really do what I need to. I received the following response from Zapier support:
"Unfortunately, Zapier does exactly work like that. A Zap is made up of Triggers and Actions (as you're familiar). In your case the Trigger is a new row in Quick Base, meaning that each new row you add after you've turned on your Zap will be turned into an event.
"Anything created before the Zap was turned on will not be pushed through the Zap. In some situations, we can work around this by using an Update Row Trigger, but Quick Base doesn't have one of those. There is currently a feature request open for it."
I suppose I can deal with the addition of new records but updating records after Zap is turned on what is of great importance to us send updates after date change.
So I am now resorting to Matthew's earlier comment:
"If you set up your google / gmail setting the right way you can send a notification (email) that has the details, and it will automatically get added to your calendar. Its more of a combo of your app notifications and google settings."
Would you be able to help me on this?
Harrison, do you have further guidance on using Zaps.
In the latest attempt, I created another table and set up two QB actions to add and update records in the child table limiting irecords n terms date range, that is, only report on projects opening next 6 months. I then established a Zap but after a lot of toing and froing with Zapier support, they were supportive though). Turns out that I cannot really do what I need to. I received the following response from Zapier support:
"Unfortunately, Zapier does exactly work like that. A Zap is made up of Triggers and Actions (as you're familiar). In your case the Trigger is a new row in Quick Base, meaning that each new row you add after you've turned on your Zap will be turned into an event.
"Anything created before the Zap was turned on will not be pushed through the Zap. In some situations, we can work around this by using an Update Row Trigger, but Quick Base doesn't have one of those. There is currently a feature request open for it."
I suppose I can deal with the addition of new records but updating records after Zap is turned on what is of great importance to us send updates after date change.
So I am now resorting to Matthew's earlier comment:
"If you set up your google / gmail setting the right way you can send a notification (email) that has the details, and it will automatically get added to your calendar. Its more of a combo of your app notifications and google settings."
Would you be able to help me on this?
Harrison, do you have further guidance on using Zaps.