Action to 'Launch Process'

How to customize your zap for launching processes on Tallyfy

This article will guide you through customizing your zap to launch a process on Tallyfy.

Considering Integration Alternatives

While Zapier can be useful for simple connections, we generally recommend more capable and cost-effective middleware solutions like n8n, Make, or Microsoft Power Automate for serious integrations.

For maximum control and flexibility, especially if you have development resources, consider using Tallyfy’s Open API to build custom integrations, potentially leveraging AI to generate code for serverless functions.

1. To begin, 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.

   

3. Connect your Google Account and select the spreadsheet and worksheet for the form data.

   

4. Select the worksheet within the spreadsheet for target data

   

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

   

6. 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

7. Select ‘Launch Process’ as the action event

   

8. Choose a Tallyfy account that hosts the required template.

   • Select the template 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

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

   

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

    

11. 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

12. 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.

    

Note on zapier dates

Please note that Zapier does not support natural languageslike 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.

Please note

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

If assignees and deadlines are left blank in the zap, whatever is set in the template 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.

Related articles

Triggers > Launch via middleware

Middleware tools bridge Tallyfy with other software by automatically launching processes when triggered by external events like form submissions or CRM updates through platforms like Make.com Power Automate or Zapier.

Launching > Launch a process from a web form

External web forms can be configured to automatically start Tallyfy processes upon submission by redirecting users to a special launch URL with form data appended as query parameters that match the exact field names in the Tallyfy template’s kick-off form.

Zapier > Automate monthly process launch with Zapier

A detailed walkthrough for automating monthly process launches in Tallyfy using Zapier’s scheduling trigger and process launch action to execute workflows on the first day of each month.

Workato > Launch Tallyfy processes from Workato

This guide demonstrates how to integrate Workato with Tallyfy to automatically launch processes by configuring HTTP connections setting up API authentication and mapping dynamic data from external systems to trigger workflows through REST API calls.