About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Records from Postgresql query not pulling by Zapier

  • 8 November 2022
  • 2 replies
  • 84 views
T

Has anyone experienced issues with custom queries using the Postgresql trigger not sending all the data?

I have an automation set up that populates a google sheet via a SQL query at a 6 AM each day. 

When I run the query locally on my db there are a handful of records that populate and it runs as expected. However, Zapier is only picking up one record instead of the multiple.

This tends to happen sporadically - sometimes the automation works as expected, other times it doesn’t. I’m a bit stumped and wondering if anyone else has run into a similar situation.

Thanks!

2 replies

Danvers
Userlevel 7
Badge +12

Hi @TryMystery, welcome to the Community!

Hmm, that is a bit of a puzzle. I took a look at know limitations and issues for Postgresql and I can’t see anything that immediate explains why it would sometimes only find one record. Are you using the new row trigger? If so, do you have an ‘Order by’ field in your Zap? It’s important to have one as it’s how the Zap can ‘deduplicate’ rows, how it remembers previous rows so it knows which ones are new/updated). Could you try adding one to see if that does the trick?

I hope that helps!

 

T

I’m using a custom query actually. Does the order by necessity come into play for custom queries as well?

Reply


Terms & Conditions