Advanced Built-In Apps by Zapier

The power of Zapier lies in using the extensive functionality made available in the built-in apps, all without using code. You can accomplish a vast array of automations using these apps. However, you will find that there will be times when you may want to achieve something with your Zaps that won’t be possible using the standard, no-code, built-in app functionality or using an existing integration in Zapier. When this happens, it is time to use webhooks, code, and API requests in your Zaps, thus opening up even more possibilities to automate your manual and repetitive tasks with Zapier. You can use Webhooks by Zapier, Code by Zapier, and API Request action steps, respectively, to accomplish this.

It is also useful to know about one of the other built-in apps that will help when you want to store and retrieve small datasets. You can use Storage by Zapier to store reference data every time a Zap runs and then share it with other Zaps by retrieving...

Technical requirements

To get the most out of the content in this chapter, you will need access to a Zapier account. The Zapier Free plan will be adequate. You will need the Zapier Starter plan to create multi-step workflows and use the Webhooks by Zapier built-in app.

Resources for understanding API documentation

In Chapter 1, Introduction to Business Process Automation with Zapier, we introduced how integrations work to request data from one application, producing a response in another. The information requests are usually in the form of creating new resources, retrieving existing ones, editing/updating existing resources, or deleting existing resources. In Hypertext Transfer Protocol (HTTP – the foundation for how data is passed along on the internet) terms, these requests are denoted as the following methods:

• POST: Used to create a new resource
• GET: Used to retrieve an existing resource
• PUT: Used to edit or update an existing resource
• DELETE: Used to delete an existing resource

As you already know, the API integrations that have been created between Zapier and other apps have specific trigger, action, and search events that you can use in your Zaps.

Although, in most cases, the integrations built with Zapier...

Webhooks by Zapier – using webhooks and HTTP requests in your Zaps

First of all, it is important to mention that perhaps the choice of name for this built-in app does not correctly describe its function, and could imply that it only works with webhooks. The Webhooks by Zapier built-in app allows you to use webhooks as instant triggers, create polling triggers, and also make HTTP requests to an API. Therefore, it is better to separate these uses by event type. Let’s look at each.

Webhooks by Zapier trigger events

As we covered in Chapter 1, Introduction to Business Process Automation with Zapier, event changes in apps are identified by either using a polling method or by using webhooks, which then cause the trigger step in your Zaps to run. The polling method involves repeatedly checking for new information at scheduled intervals. However, with webhooks, you provide the app with a URL that your originating app constantly monitors for new events, thus receiving information...

Using the API Request action event (feature in beta)

Using Webhooks by Zapier might seem quite complicated, especially if you have to decipher API documentation. A more straightforward approach is to use a new feature that is currently in beta throughout the platform. Zapier has begun upgrading certain integrations with the API Request (beta) action event. Before the release of this action event feature, users would need to extensively understand API documentation and use the Webhooks by Zapier built-in app to make PUT, GET, and POST HTTP requests. The introduction of this new action event in many app integrations allows API requests to be made in a simpler, no-code-focused fashion. Unlike with using Webhooks by Zapier, you will have already connected the app to your Zapier account and will not need to provide any further authentication details, such as an API key. In many cases, you can make simple HTTP requests without having to understand complex API documentation jargon. You will...

Using App Extensions in multiple Zaps (feature in beta)

If you use the same API Request (beta) action steps in several different Zaps, you will need to replicate the information from one Zap to another normally. However, the App Extensions action event takes the capabilities of the API Request (beta) action event feature a few steps forward and allows you to create app extensions in the App Extensions builder, allowing you to set up API call settings that can be used in multiple Zaps. As with the API Request (beta) action event, the App Extensions (beta) action event allows you to use your already authenticated app connection information, so all you have to do is create an App Extension template that can be used in multiple Zaps, and shared in your team if you’re using a Team or Company account. As with the API Request (beta) action event, the App Extensions (beta) action event is currently available for use with a limited number of apps. You can find the list of supported apps...

Code by Zapier – using JavaScript or Python code 
in your Zaps

The next step up from using webhooks and API requests in your Zaps is to use code when you can’t achieve what you need to with the no-code built-in apps, Webhooks by Zapier, or API Request action steps. You can write custom code in either the JavaScript or Python programming languages and use it in your Zaps with Code by Zapier to either trigger the workflow or perform various tasks to transform and customize your data.

The Code by Zapier built-in app can be used via the following trigger and action events:

• Run JavaScript (trigger): This trigger event allows you to use JavaScript to start a workflow
• Run Python (trigger): This trigger event allows you to use Python to start a workflow
• Run JavaScript (action): This action event allows you to run JavaScript as an action step in your Zap
• Run Python (action): This action event allows you to run Python as an action step in your Zap
...

Storage by Zapier – saving and storing data

There may be many scenarios where it would be useful to be able to store small sets of data for use in your workflows. The Storage by Zapier built-in app allows you to save and retrieve small data values. With it, you can store reference data each time a Zap runs and then share it with other Zaps by retrieving it.

Storage by Zapier does not operate with user accounts. Instead, you must specify a secret storage key in the format of a Universally Unique Identifier (UUID4), which acts much like a password, to identify and group storage data. You would then use this secret storage key to identify where to add data to and retrieve data from. By doing this, you can have multiple storage keys that identify your storage locations.

You can store individual values or lists of values. You can also use child values (nested values of data) if you want to store and retrieve several values related to a unique identifier – for example...

Summary

In this chapter, we discussed three advanced built-in apps by Zapier and a new feature in beta. We began by reviewing how to use webhooks in your Zaps with Webhooks by Zapier and make HTTP requests. Then, we explored how to use the API Request action event feature (in beta). Next, we covered how to use JavaScript or Python code with Code by Zapier, and generate code with ChatGPT. Lastly, we explored how to use Storage by Zapier to store and retrieve data.

You now understand what the Webhooks by Zapier, Code by Zapier, and Storage by Zapier built-in apps, as well as the API Request action event, can be used for.

In the next chapter, you will learn about the two built-in apps that can be used for managing your Zapier account: App Status by Zapier and Zapier Manager. We will cover how to use App Status by Zapier to get notifications of integration issues and review the various trigger, action, and search action events that Zapier Manager has for managing errors and changes...

Questions

1. Which three built-in apps or features in Zapier can be used to make HTTP requests?
2. If you would like to store small values secretly and securely, what Zapier built-in app can you use?