Are there any errors in the logs or did it just stop working?

that seems odd. 

Oh sorry just saw you quickly replied to this ​@DannyPancratz! Yes, the error is due to the token expiring I think (and see with my limited technical abilities) did you happen to have this challenge? 

Do you know where it is broken? Is it not triggering? Or is it it triggering, but there are errors in subsequent steps? 

If it’s the latter and a token expiration issue, my recommendation is to use this Zapier action for Gainsight CC actions (rather than webhooks by zapier for API calls) 

With this, you shouldn’t need to authenticate with the Gainsight CC API, it’s built into the integration/action. That both saves you Zapier steps and avoids the token expiration issue. 

It’s triggering yet errors in the subsequent steps - and having to create a token I need to rely on some team members each time so let me give this a go actually thank you so much  !

Hi! Yes, this happens sometimes. Usually, it’s due to the Zap losing authentication, hitting a task limit, or the trigger app not sending new data. I’d recommend checking the Zap history for errors, reconnecting your accounts, and verifying that the trigger conditions haven’t changed. Often, just reconnecting the apps and turning the Zap off and back on fixes it. If it still doesn’t work, Zapier support can help troubleshoot with your specific Zap ID and task history.