Hi @GorkEvenUp, welcome to the Community! 

Webhooks are more advanced than standard app triggers and actions as you’d need to reference GitHub's API documentation to determine which fields and parameters are required.

Are you wanting to set up a Zap to trigger when a new repository event happens?

If so, perhaps you could use the existing New Repo Event trigger for GitHub instead of setting up a webhook. Judging by the description the New Repo Event trigger should allow you to “listen” for any event that happens on a repo: 

Then you could add a filter to the Zap to ensure it only continues for certain types of events. If you’ve not worked with filters in Zaps before you can learn more about them here: Add conditions to Zaps with filters

Do you think that approach could work? If I’ve misunderstood what you’re looking to do with this workflow or you run into any trouble on that please let me know!

Sam, thank you for the answer. To clarify, I was interested in triggering a workflow via Zapier. I managed to do it via a POST event by ‘Webhooks by Zapier’. My only concern now is to store my Github token properly. Currently it’s fed into my action as plaintext, can I use a secret storage of some kind and pull it from there? 

Thanks for clarifying that @GorkEvenUp! In that case I’ll move this over to the Code & Webhooks section of this Community.

You could use Storage by Zapier to store the secret. Storage by Zapier has a Get Secret action that could be used to retrieve the secret to be passed to the Webhook action.

Hope that helps. Please do reach back out if you run into any issues on that or have any further questions!