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.

Best answer

Stripe GET balance transactions API call in zapier greater than or equal a unix timestamp issue

  • 14 August 2023
  • 8 replies
  • 146 views
MattBia
Userlevel 1

Hey all, 

 

New to Zapier and API Calls. I am trying to retrieve a list of Stripe_fee balance transactions within the last 7 days of when the zap is trigged.

 

In the stripe API docs it mentions I can use a child parameter “created.gte” to return results where the “created” field is great than or equal to this value (value hopefully being a dynamic Unix timestamp that I pull from a previous action. I am guessing, but do you use a double underscore to signify a nested (child) parameter?

 

STRIPE API doc about created parameter
current settings successfully returning a list without regard to the created limitation.

 

This correct returns the last 10 stripe fee transactions but does not filter or take into account the created parameter. What am I doing wrong?

 

Thank you for any help!

icon

Best answer by Troy Tessalone 15 August 2023, 01:42

View original

8 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @MattBia 

Good question.

What is the link to the Stripe API endpoint you are referencing?

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
MattBia
Userlevel 1

Hi Troy,

 

As in the Stripe API docs?

https://stripe.com/docs/api/balance_transactions

Troy Tessalone
Userlevel 7
Badge +14

@MattBia 

Looks like the URL is using an outdated structure.

 

 

You may have to deal with pagination if there are 101+ results.

 

For Created, try changing the left side to just created, then add the JSON to the right side. (remove any conditions you don’t need)

{
    gt: null,   // Greater than
    gte: null,  // Greater than or equal to
    lt: null,   // Less than
    lte: null   // Less than or equal to
  }
⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
MattBia
Userlevel 1

@Troy Tessalone 

I updated the URL and tested without any created parameter and that was successful. 

I attempted the do what you said for the created and got this. Mind you I could be completely off with what I entered here because I have zero JSON experience. 

 

Troy Tessalone
Userlevel 7
Badge +14

@MattBia 

replace null with the mapped output.

{gte: 0000000}

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
MattBia
Userlevel 1

@Troy Tessalone 

Did both of these resulting in the same invalid integer error:

 

Troy Tessalone
Userlevel 7
Badge +14

@MattBia 

Give this a try:

Left side: created[gte]

Right side: mapped variable

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
MattBia
Userlevel 1

@Troy Tessalone 

 

That’s it! THANK YOU!!!!!!!!!! 

 

Reply


Terms & Conditions