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

Greenhouse to Zapier Workflow Issue: Slack Notifications for Internal Job Openings

  • 22 June 2023
  • 8 replies
  • 59 views
JoshJosh

I'm currently experiencing an issue with an automation workflow between Greenhouse and Zapier. The workflow is designed to create a Slack notification whenever there's a new internal job opening in Greenhouse. Despite my Greenhouse API key having all the necessary permissions (which I have double-checked), the "New Job" trigger in Greenhouse is not sending data to Zapier as expected. This is preventing the intended notifications from being posted on Slack.

I'm interested in hearing from anyone who has faced similar issues with the integration of Greenhouse and Zapier, particularly with the "New Job" trigger. Any advice or suggestions for troubleshooting this problem would be greatly appreciated. Keeping our team promptly informed about new internal opportunities is a priority for our operations, and this automation plays a significant role in that process. Thank you in advance for your help and insights!

8 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @JoshJosh 

Good question.

The Greenhouse Zap triggers are all scheduled, meaning those can take from 1-15 minutes to fire, depending on your Zapier plan.

Check your Zap Runs history to see if the Zap fired and encountered errors: https://zapier.com/app/history/

 

 

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

Hi @troy

There’s nothing in the history, so I know its because the Zap isn’t getting triggered at all.

I’m hoping there’s some deeper info to be shared about the Greenhouse side and its ping to Zapier.

Thanks

Troy Tessalone
Userlevel 7
Badge +14

@JoshJosh 

Greenhouse status page: https://status.greenhouse.io/

This may be related.

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Troy Tessalone
Userlevel 7
Badge +14

@JoshJosh 

A workaround is to use webhooks in Greenhouse.

Guide: https://support.greenhouse.io/hc/en-us/articles/360005574531-Create-a-web-hook

Zap trigger: Webhook - Catch Hook

This will provide the unique webhook url to configure in Greenhouse.

 

 

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

Ah thanks Troy!

It’s not been working for a week now, I’ve been trying different things, so not sure if the current status is the case, but let me try the web hook option now - can’t believe I didn’t think of that, thank you!

shalgrim
Userlevel 6
Badge +8

Hi @JoshJosh,

Do you have a lot of job postings? Like, a few hundred? We’ve noticed this happening with other users who have a lot of job postings due to the way the job listings are sorted.

It’s a known bug and the main community thread is here.

If setting the Limit to Live Posts parameter would still meet your needs, I recommend turning that on. Another possible workaround would be to set up Greenhouse to send an email on a new job posting and then have a Email Parser step be your Zap trigger.

In any case, I’ve added your email to the list of affected users, so when there are any updates you’ll know right away.

JoshJosh

Hi @shalgrim.

We only have 60-70 postings. I’ll try switching it to “Live Posts” only and see if that makes a difference, but I’m pretty sure I tried and that wasn’t unfortunately working.

I’m just trying the webhook method, but there isnt any information coming through the test of the webhook that I can use (e.g. job title, location, etc) - do I need to wait for a real job post to be created to be able to use the placeholders of this webhook info in the next step of the zap (send to slack)?

If that doesn’t work, I’ll try the email method.

Thanks for your help!

shalgrim
Userlevel 6
Badge +8

> do I need to wait for a real job post to be created to be able to use the placeholders of this webhook info in the next step of the zap (send to slack)?

Probably, yeah. Let us know if that doesn’t work out!

Reply


Terms & Conditions