You can use Zapier to connect any one of Zapier's 2,000+ integrated apps directly to Woodpecker without any code! (Learn more about Zapier).
We'll walk through setting up a simple Zapier Zap example below. Keep in mind that this example is just one of the many workflows you can set up with Zapier. Almost any ideal workflow between apps that you can imagine, you can represent in Zapier.
Before you start
Before you set up your first Zapier Zap, you'll need to make sure that you've:
Created a Woodpecker template (if you haven't follow this guide here).
Saved that template to your Document Collection (more info on how to do this here).
Make sure you have a Woodpecker API key (need an API Key?).
Setting up Zapier with Clio & Box
In this example, we'll walk through setting up a Zapier Zap that takes Clio data, populates a Woodpecker template with it, stores the final templates in Box, and sends us an email notifying us that the documents have been prepared.
After signing into your Zapier account, click the "Make a New Zap" button.
Set up the Zap "Trigger" (Clio)
You'll then be prompted to specify the "Trigger" for your Zap.
For this example, we're going to use Clio as our trigger. Search for "Clio" in the search box and select the Clio app.
For the "Trigger Event" we're going to choose "New Task" to indicate that we would like this Zap to start whenever a new Clio task is created. You can choose any "Trigger Event" you like, but for this example, we'll keep it simple.
You can filter which tasks will trigger this Zap by adding in a Zapier filter step immediately after the Clio step. Set up the filter step to only allow certain types of tasks or tasks with certain names to pass through. We'll leave the filter step out of this example for simplicity.
You'll then be prompted to sign in with a Clio account:
You'll then be walked through pulling in a sample Clio Task into Zapier so you can model the rest of your Zap based on this data.
Set up the first Zap "Action" (Woodpecker)
After you've set up Clio, click the "Do This" box to add an "Action" step.
Search for "Woodpecker" and select the "Woodpecker (1.0.0)" app.
You'll then be prompted to sign in with your Woodpecker account.
Enter your API Key in the corresponding popup window. Need an API Key?
After you've authenticated your Woodpecker account, you'll be able to designate which Woodpecker templates should be populated with the Clio data you've pulled from the first step.
In the "Documents" dropdown, select a document you'd like to populate. To select multiple documents, click the "plus" button on the right.
Remember: You'll only see templates in the "Documents" dropdown that have been saved to your Document Collection. If you don't see a template in the dropdown, open the template in Word, launch Woodpecker, and save that template to your collection.
After you've selected the documents you'd like to populate, click the "Refresh fields" button to display a list of the unique fields across the templates you've selected.
You'll now see a list of the unique fields across the templates you've selected to be populated.
Note: Conditional, formula, or hidden fields will not display in this list as these fields are automatically calculated and do not require user input.
Either manually enter information into each input field or click the "insert" button on the far right of an input field.
You'll then be prompted to test the set up you've created. Once you get a successful test result, click "Done Editing." Having trouble testing your Zap? Let us know and we'd be glad to help troubleshoot.
Setting up additional Zap "Actions" (Box and Gmail)
To add Box and Gmail to the workflow, we'll follow very similar steps that we just walked through to set up Clio and Woodpecker. For that sake of brevity, we won't walk through the full set up of these two apps but instead, show the highlights.
First, click the "plus" button below Woodpecker to add additional apps.
Choose "Box" and "Upload file" for the "Action Event."
Select the "zip link" from the Woodpecker step for the "File" input box.
Once you've tested and confirmed the file was uploaded successfully, click "Done editing" and move on to the final step.
Click the "plus" button below the Box step to add our final step, Gmail.
Choose "Gmail" and "Send Email" for the "Action Event."
In this example, we want to simply send ourselves a notification email when these documents are populated and we'll also include the documents as an attachment.
Alternatively, you could email the final documents to a client or notify yourself via any other app that you prefer.
Once you've tested and confirmed that the email was successfully sent, click "Done editing".
You should now see all of the steps you've created for your Zap. All that's left to do now is turn it on!
You're all set!
Once you've turned your Zap on, anytime a Clio task is created the entire Zap will run: (1) the Woodpecker templates you've selected will be populated with the information from Clio, (2) the final Woodpecker templates will be stored in Box, and (3) you'll be notified via email that the documents have been populated and saved.
Zapier will email you if it runs into any trouble processing the Zap and will provide clear instructions for fixing it. If you need any help troubleshooting a Zap, let us know, we'd be glad to help out.
This example is just one of the many example workflows you can set up via Zapier. Once you're comfortable with the Zapier interface, feel free to experiment with integrating more apps with Woodpecker or any other app. Let us know if you'd like any help setting up your own custom Zaps!