Consumption of Credits

[SpyrosTsouk]

Hi Latenoders,

Thanks for your help!

I want to be able to run a lot of iterations of a scenario that:

• goes to linkedin and gets data through profile urls
• edits the data with JS code
• then saves them in Google Sheets

But

I have noticed that my scenario consumes more credits than expected

1. Does e.g. the Find Row & Update Row actions consume a lot of credits, when run e.g. for 15 columns? Or is the linkedin data scrapping that consumes the credits?
2. Is there a way to do it and consume less credits?

I can skip the Find Row and Update Row actions and just drop the data in a new sheet, and then run everything with Google Sheets functions.

Screenshot attached!

Thanks!

[TimePaste.com]

The LinkedIn Data scraper is plug-and-play, meaning it uses credits but you don’t need to deal with the hassle of authentication or API tokens. The credit usage is displayed if you open the node.

[SpyrosTsouk]

I’m aware of that @TimePaste.com, I got the impression it consumes more than that.

Like 50, 60 extra or something

Overall, what setup makes more sense in such a case to scale the process?

Meaning I want to scrap and move let’s say 500 profiles

[TimePaste.com]

In your screenshot, the node is part of an iterator, so each time it is iterated over, it will consume 11 credits. The screenshot shows 9 iterations, meaning the overall scenario would be around 100 credits used. Are you seeing more usage than that?

As for scaling to 500, you could run that in Latenode but it will be 5500 credits just for the LinkedIn scraping, so depending on the frequency you need to pull that data, you may want/need to check into other ways of retrieving it.

[SpyrosTsouk]

I just reviewed it

And I think the credit consumption is good now

How else would you recommend I could get this info?

[TimePaste.com]

This isn’t the appropriate place to offer alternatives, however if you want a consultation, we can recommend options in a focused discussion about your project.

As you’ve noticed, Latenode makes it easy and convenient to integrate LinkedIn data scraping into your workflows with its plug-and-play node which does not require any additional authorization parameters. Other options exist but would not be as seamlessly integrated or easy to use as this built-in node within Latenode.

[Oleg]

You could check credits consumption for Plug n Play nodes in the Logs tab

[SpyrosTsouk]

Thanks Oleg, I didn’t know that!

@TimePaste.com, I thought we were talking within Latenode

Thank you both!

[Raian]

To be fair, it’s almost impossible to find LinkedIn scraping cheaper than on Latenode. For example, using the same service on Clay would cost several times more. Consequently, any intelligent automation will pay off in the long run. Just consider that 11 credits at $0.0019 per credit equals only 2 cents!

2 cents for a potential lead or partnership