Instant Triggers
Triggers kick off the entire Automation by responding to a specific event or condition. When the trigger event or condition occurs, viaSocket detects it.Â
Instant triggers initiate actions immediately upon the occurrence of a specified event. These triggers provide near-instantaneous responses to events within integrated applications.Â
        
At the core of Instant Triggers lies the concept of webhooks. Unlike traditional APIs where you periodically poll for updates, webhooks are HTTP callbacks initiated by events. When an event occurs, such as a form submission or a new record creation, the corresponding webhook sends a payload of data to a predefined URL. viaSocket seamlessly integrates with webhooks, allowing users to create automation workflows triggered by real-time events.
         
How Instant Triggers Work in viaSocket:
- Let's consider a scenario where you choose an instant trigger to trigger your workflow through an app integrated with our platform.Â
For example, you want to trigger a workflow whenever a new deal is created in Pipedrive. - So, whenever a new deal is created in Pipedrive, it triggers a webhook, sending relevant data (such as the deal’s details) to your flow in viaSocket.
         Â
- viaSocket receives the webhook payload, interprets the data, and initiates the workflow that you set up, such as creating a new task in a project management tool or sending an acknowledgement email to the customer.
- The automation workflow executes instantly, ensuring prompt response to the new deal created in Pipedrive without any manual intervention.
📌 More examples:
- Instantly sending a notification when a new email arrives in the user's inbox.
- Automatically updating a CRM record as soon as a new lead is captured on a website.
- Instantly triggering an action in response to a customer's interaction with an online form.
Each application's API defines the type of triggers it supports. Most APIs offer methods for polling data, for applications to support instant triggers, they must offer webhooks.Â
In essence, viaSocket adheres to the capabilities provided by each application's API to determine the type of triggers available for automation. If an application supports webhooks, viaSocket can leverage instant triggers for real-time automation, whereas applications without webhook support will rely on polling triggers to periodically fetch updates.
