Skip to main content

Hi we’ve created a Zap between Recruitly, our CRM, and Clockify where if a new role is created on Recruitly it creates a matching project on clockify. This has worked seamlessly for over a year and yet suddenly the trigger has stopped working. 

 

The Recruitly trigger (new job created) does not fire any more when a new job is...created. Recruitly tell me nothing has changed at their end - anyone else experienced issues like this, and have any suggestions on bringing the trigger back to life?

 

I’ve tried re-creating the Zap run, refreshing the connections with both Recruitly and Clockify, and asking the tech support team at Recruitly to investigate - all to no avail. 

Hi and welcome to the Community, ​@charityman! 😁

Sorry to hear you Zap suddenly stopped working! I checked and the New Job Created trigger is an instant rather than polling type of trigger, so the Zap should trigger when Recruitly send over the information about the new job that was just created. 🤔 

As was successfully triggering before, my guess would be that either we’re not being sent the information from Recruitly or, there’s a bug that’s preventing the Zap from triggering. Your best bet here will be to reach out to our Support team to investigate this further. They’ll be able to check the logs for your Zap to determine if it’s a bug and can confirm whether anything was received from Recruitly. And if it is a bug they’ll be able to open a bug report on your behalf to get it sorted.

Keen to ensure this gets sorted so please let me know how you get on with them!