Connecting Zapier or Make

Everything you do on OmniSchema's side to connect Zapier or Make: the key, the role, and the connection their triggers make.

What's in this video

1. Zapier and Make link OmniSchema to thousands of other tools, without any code. This video shows everything you do on OmniSchema's side. Start in Governance, under API keys.
2. Make a key just for Zapier or Make, and name it so you'll recognise it later, like Zapier.
3. Choose a role that can see the lists you want to use. For triggers, like a new row, and for searching, Read only is enough. If Zapier or Make will add or change rows, choose Read and write.
4. Click Create key, and copy it. We've hidden it in this video.
5. In Zapier or Make, add the OmniSchema app, and paste the key into the field called API key. The connection is named after your company and the key, so you can tell your keys apart.
6. When you switch on an instant trigger, like New or updated row, a connection appears by itself on that list, in Connections and Feeds. Let's look. Open Databases, choose your database, and click the list.
7. Open Connections and Feeds. Here it is, marked Made by API key, with the key's name. Its deliveries show every row sent to Zapier or Make.
8. Turn the Zap off, or delete the scenario in Make, and this connection goes by itself.
9. People and Purchasing work the same way, as long as they're switched on and the key's role can see them. Purchase requests raised this way show the key's name as who sent them.
10. If a Zap or scenario stops working, check the key in API keys first. It may have been revoked, or reached its stop date.