Working with Zapier
With hundreds of apps available, Zapier is a great way to set up integrations that aren't part of the native ProdPad roster. The best part? You don't need to rely on your development team to set this up for you - you can do this yourself!
Each zap you set up is based on a trigger and an action.
The trigger is the function that will need to occur in order for the action to follow.
For example, if you wanted to send feedback from your help desk to ProdPad - the triggered app would your help desk, and the action would be to send that data to ProdPad.
Each app can be set up with defined triggers and actions that can be specified to create particular objects, ensuring that you can flexibility and control over your integration.
Create a Zapier integration
There are two ways of creating a Zapier integration.
The first is a trigger-based action. This involves having an application as a trigger, and a receiving application with an action. If you're looking to push items into ProdPad, it is likely ProdPad will be the receiving action (for example, when creating feedback from another application.)
Some of our most popular trigger-based actions zaps are:
The second method is a push action, where ideas or stories can be pushed from ProdPad into a third party application. To use this option, you would select the 'pushed idea' or 'pushed user story' from the Zapier options, which will then create Zapier as an available integration within the 'Push to development' slideout in ProdPad.
To create either option, you will need a ProdPad account and your personalAPI key.
Some Zapier integrations will require a paid Zapier account.