Pabbly Storage Module Request (Zapier has this available)

[juancolicchio]

Zapier allows you to quickly store and retrieve small values of data. Allows you to reference data between Zap runs or share data between different Zaps (https://zapier.com/apps/storage/help)

The use case:

Array of all customer invoices are generated.
Filter unpaid invoices by status
Store each unpaid invoice information
Run spreadsheet calculations on the stored data

 

[Pabbly]

Hey @juancolicchio

You can upvote the same feature request here - https://pabbly.hellonext.co/b/Integration-Request/p/storage-feature-like-zapier

Thanks!

 

[Nikol' Mora]

Oh my, Pabbly still doesn't have this Was looking to switch from Zapier but there's absolutely no way I can without a solution to this.

 

[finanzfroh]

Hello @Pabbly

A few years have passed and this feature does not exist. The feature request is on hold.
Would you please give a short update on this? I would be very interested in the feature.

 

[Fagun Shah]

Hello @Pabbly

A few years have passed and this feature does not exist. The feature request is on hold.
Would you please give a short update on this? I would be very interested in the feature.

They launched the variables -

 

[finanzfroh]

They launched the variables -

Many thanks for the tip!
However, this is not like the Zapier storage.
I need some kind of buffer for automation. The background is that customers can also pay in installments. However, the customer is only named with the ID at the time of purchase. For all other installments, only the ID is required. For allocation, it would therefore be necessary if the customer and ID could be stored in a temporary memory for approx. 3 to 6 months and then deleted again. In my opinion, this would not be possible with a variable - as there could be several customers.
Then I solve it with a Google spreadsheet.

 

[Fagun Shah]

Many thanks for the tip!
However, this is not like the Zapier storage.
I need some kind of buffer for automation. The background is that customers can also pay in installments. However, the customer is only named with the ID at the time of purchase. For all other installments, only the ID is required. For allocation, it would therefore be necessary if the customer and ID could be stored in a temporary memory for approx. 3 to 6 months and then deleted again. In my opinion, this would not be possible with a variable - as there could be several customers.
Then I solve it with a Google spreadsheet.

It can be possible with variable, if you store it as an array, but it will be complex.

Google Sheet is better for now.