ShotGrid Webhooks + Zapier workflow - 2022

I created an article in 2017 SG Webhooks + Zapier Webhooks + Send Email. Now, there are some updates on both ShotGrid and Zapier. Create this article to address the different.

The workflow uses ShotGrid Webhooks and REST API

Setup in ShotGrid

ShotGrid Webhooks setup doesn’t have any change. Please follow SG Webhooks + Zapier Webhooks + Send Email - Setup Shotgun Webhooks.

Let’s focus on the different.
When ShotGrid migrate to Autodesk Identity, there are two different account.

  • ShotGrid/RV/Create/Toolkit account. This is Autodesk account. User can mange password in

  • Python API/Rest API human user. This is legacy ShotGrid user. User need to create PAT. And manage user name and password in Account Settings - Security

  • Try to avoid to use html characters (%, # …) in legacy password. Zapier won’t escape those characters. (Maybe there is trick. But I don’t know)

In this workflow, we need the second one Python API/Rest API human user. When legacy user/password created. Highly recommend to test with PostMan to test. If PostMan could pass the test, the account will be working for Zapier.


We will only show the first four steps

1. Catch Hook

Zapier will try to capture data from ShotGrid.

Choose app

Setup up trigger

Test Trigger

2. Only Continue if…

Setup some condition to test if Zapier get correct data to save traffic.

Choose app

Filter setup & testing


On this step, Zapier needs to get access code from ShotGrid legacy username/password.

***Note: Before you start this step, test your legacy username/password with PostMan ***

Choose app & event

Set up action

Test action

4. GET

On this step, Zapier will get data from ShotGrid

Choose app & event

Set up action

Test action