Three Ways to Deploy Custom Actions

Zapier's "click and create" interface is a good choice for basic automations where your goal is sending assets, comments, or status events from Frame.io to popular apps or productivity tools.

Pros

• Simple to use. Point and click to create automations.
• Task history is Zapier's runtime log tool and summarizes data I/O for each workflow step on every automation run.
• Paying for a premium account unlocks Paths, a tool for building adding forking logic to automations.

Cons:

• Zapier's support for webhooks is restricted in that it won't support detailed messages or any interaction back to the Frame.io user when your Custom Action runs. The limitation is explained in the Zapier support docs:

We [Zapier] always return a success message with a payload of debugging information when collecting a webhook - regardless of whether there is a Zap behind the webhook or if it is paused or not...There is no way to customize the response to the request you send to the Catch Hook URL, as the response is sent before the Zap triggers and runs on the webhook request.

• Zapier's UI can be tedious when verifying Custom Actions are functioning properly. For example, Test Data needs to be checked and refreshed while testing; if test data doesn't match your live data, Zapier may throw 'false negatives' and show errors even when your Zap design is actually correct. If a critical piece of data such as File URL is not available when a Task expects it, your Zap may error out or not function as expected.