Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hi all!

I’ve set up the following zap. My plan wasto:

  1. Use Octoparse to scrape job postings from LinkedIn. This happens once a day and should bring back like 700-1000 jobs.
  2. Send the structured data to an Airtable.
  3. Send it to ChatGPT for it to interpret the job postings and create tags.
  4. Update the data in Airtable with the tags.

My challenge is that this setup killed my task number in one night. I guess every job posting that ran through, counted as its own task? What did I do wrong here? How might I remake this so that I’m not creating 1000 pages of zap runs in one night? See the Zap Runs history.

 

This is the workflow
1000 pages of runs! Look at the dates here.

 

Hi @khou 

Zap Trigger: Octoparse - New Data Processed

Looks like the Zap triggers for each new row and triggers at the same time from Octoparse.

 

Help link for how Tasks are counted in Zap Runs: https://help.zapier.com/hc/en-us/articles/8496196837261-How-is-usage-measured-in-Zapier

 

TIPS:

  • Consider adding a Filter as Zap step 2 to include only rows of data you want to process
  • You probably also want to add a Delay (After Queue) as Zap step before the first Airtable step to make sure API limits are not hit for Airtable and ChatGPT

 

Reply


Terms & Conditions