Zapier gives customers the ability to integrate web applications to build automated workflows. It enables cloud-based applications to communicate with each other.
When applications are tied together through Zapier, these workflows are known as “Zaps”.
In order to create a Zap, you need to designate an application as the “Trigger”. This initiates & results in a subsequent “Action”. Depending on the app, the Action can happen in both the same or a different application.
When you log in to Zapier and select an application, you will see a list of Triggers & Actions that are supported.
Trigger – A Trigger is what needs to happen for the Zap (or Workflow) to Start. When something occurs in one application (such as creating an appointment in Outlook) the Trigger is activated.
Action – What happens once the Trigger occurs. The Action is a “reaction” to what was initiated by the Trigger application. For now, Woodpecker is used exclusively as an Action within Zapier.
Zap – The Workflow that has been created when successfully establishing a Trigger Application followed by an Action.
Woodpecker Trigger - When someone submits a Woodpecker Questionnaire, you can connect their responses ( and the populated document(s) with other platforms.
Submit a Woodpecker Questionnaire and create a New Matter in Clio
Submit a Woodpecker Questionnaire and create a New Lead in CASEpeer
Woodpecker Action - When you're using another platform and want to connect the responses with Woodpecker Templates
Submit a Jotform Intake and populate Woodpecker Templates
Submit a Lawmatics Intake and populate Woodpecker Templates
Create a task in Clio and populate Woodpecker Templates
Here you can find all of our pre-built Zaps.