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 login 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.
With its powerful & seamless ability to populate documents, Woodpecker is used as an Action when connected to other applications within Zapier.
The best way to get more out of Woodpecker through Zapier is to think of the applications you use most, and how a function within one of those applications can launch the population of documents within Word through Woodpecker.
An example of this would be through creating a contact in an application such as Outlook. Once the contact is created, it can be used as a Trigger in Zapier to have a document such a Client Engagement Letter automatically populated with the client's data. This is one way you can use Woodpecker to streamline a process such as Client Intake.