PROCESS > How do I create and customize a 'Launch Process' zap?

This article walks you through the process of customizing your zap for a 'Launch Process' use-case.

You can set a number of attributes in your zap with the data pulled in from the webhook or data fields from the integrated app.

Let's look at this process with the help of the following usecase:

Employee requests leave through a Google form which triggers an approval process in Tallyfy

1. Create a new zap and select 'Google Forms' as the app for Step 1

2. Use 'New or Updated Response in Spreadsheet' as the Trigger for this step

3. Connect your Google Account which hosts this form

4. Select the spreadsheet that documents all responses for the above form

5. Select the worksheet within the spreadsheet for target data

6. Pick a sample response. (This step assists in automatic form filling in the next step of the process)

7. Now you are setting up the action steps (Tallyfy Launch Process) for the trigger encountered (every time someone fills in the leave request form). Choose Tallyfy as the action App

8. Select 'Launch Process' as the action event 

9. Choose a Tallyfy Account that hosts the required blueprint ( how to connect my Tallyfy account to Zapier)

- Select the blueprint from the options available

- At this point, you can customize the process name. This name will be assigned to the process when the zap is triggered. In our example, we have used the employee's name from the Google form and the timestamp the request was submitted to create a dynamic process name

10. You can also customize any process notes to be entered

11. You can customize and fill in data into the Tallyfy process using data from the Google form

12. You can also customize step assignees. Step assignees can be members of your Tallyfy org or guests (external users). In our example, we have used the contact email address of the employee from the Google form to assign additional tasks

13. If there was a date field in the Google form that would have corresponded to a suggestive deadline, we can customize deadlines in this zap too. 

Please note that Zapier does not support natural languages like 2 days, 2d or 5 weeks, and so on. That means, a deadline like {April 29, 2020 10:000:00 -2d} will throw an error. 

For reference, the blueprint used for the above use case is as follows:

Please note: 

Custom entries assigned in the zap will override blueprint level attributes such as assignees, deadlines, form values etc.

If assignees and deadlines are left blank in the zap, whatever is set in the blueprint will be inherited.

A note on passing checklist items through to the zap

When you need to fill out a checklist when launching a process via our zap - ensure you use a comma-separated set of values from the original source, and then pass that straight through to the checklist. The result will be intuitive - the items you passed in will be the values which are "checked" in your checklist form field.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us