Webhook scenarios

When to use webhooks

Webhooks enable data collection during a process and transmission to another service.

When a process is launched

For template-level webhooks, a webhook is triggered immediately when a process is launched, before any tasks are even completed. This allows you to track new process instances as soon as they are created. It’s a great way to keep track of the progress and gather important data right from the start.

When a specific task in a process is completed

This webhook triggers when a specific task is completed. It allows you to stay updated on important milestones in your process.

If you want to see more examples and learn how to use our webhooks, watch our tutorial videos below. They demonstrate practical use-cases and provide step-by-step instructions.

Example: How to export data from a task to a spreadsheet

This video demonstrates how to export form field values from Tallyfy to a spreadsheet using Zapier.

Considering Integration Alternatives

While Zapier can be useful for simple connections, we generally recommend more robust 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.

Example: How to automatically launch a new process after a task is completed

This video shows how to configure a webhook to automatically launch a new process when a task is completed.

Example: Send form field data from multiple tasks via a webhook

This video demonstrates connecting a Tallyfy template to a middleware system to send form data from previous steps to other services.

Example: How to send an email to anyone when a task is completed

This video shows how to trigger an email notification when a task is completed using webhooks and middleware.

In case you’re curious about the information passed along in a webhook, please refer to the table below for details:

📌 Webhook-Sample.json ↗

Tallyfy allows you to choose between two date formats for your webhooks. Take a look at the screenshots below to see how they appear:

A note on security - our webhooks come with a header X-Tallyfy-OrgID which contains your organization ID - offering an extra layer of authentication.

Related articles

Webhooks > Details about webhooks

Tallyfy’s webhook system enables real-time data transmission between processes and external applications through template-level or step-specific triggers that send JSON packets to predetermined URLs for automated integrations and notifications.

Integrations > Webhooks

JSON-formatted webhooks enable instant data transmission between Tallyfy and external systems by sending automated notifications when specific events occur within processes.

Webhooks > Send emails using webhooks

Automated email notifications can be set up using Tallyfy’s webhook functionality to trigger customized messages through middleware platforms when specific workflow events occur.

Launching > Launch a process from a web form

Tallyfy enables automatic population of process fields by connecting web form submissions to workflow initiation through URL parameters and matching field names.