Flows
Discover how to automate your workflows seamlessly with viaSocket Flow

The "Response" in viaSocket enables users to set responses for webhook URLs, dictating the behavior when the URL is accessed. Whether users prefer a default response provided by viaSocket or desire a customized response tailored to their specific needs, this feature offers flexibility and control over webhook interactions.
Key Features:
Default Response: viaSocket offers a default response option, providing users with a quick and convenient way to set a standard response for their webhook URLs. This default response can be easily configured within the viaSocket interface.
Custom Response: For users seeking greater customization, viaSocket allows the creation of custom responses. This feature empowers users to define the exact content and format of the response, enabling them to meet unique requirements and integrate seamlessly with their existing systems.
How it Works:
Default Response:
Users can select the default response option within the viaSocket webhook configuration.
The default response is automatically sent whenever the webhook URL is accessed, providing a consistent reply without additional configuration.
Webhook Response
Apr 30, 2025Triggers kick off the entire Automation by responding to a specific event or condition. When the trigger event or condition occurs, viaSocket detects it.
When setting up triggers on viaSocket, it connects to the API of the respective application to retrieve information about trigger events. viaSocket relies on the capabilities provided by that API. The type of trigger available (whether polling or instant) is determined by how the application's API is designed.
While Instant Triggers excel in real-time event-driven automation, Polling Triggers offer a different approach, particularly suitable for scenarios where real-time updates are unnecessary or impractical. Polling Triggers involve periodically querying an external data source, typically through APIs, to check for updates or new information.
Polling triggers involve regularly checking for updates or changes within an application at predefined intervals. Instead of responding immediately to events, these triggers periodically scan for new data or changes.

APIs (Application Programming Interfaces) serve as the bridge between different software applications, allowing them to communicate and exchange data. With Polling Triggers, viaSocket interacts with external systems through their APIs, retrieving relevant information at predefined intervals.
How Polling Triggers Work in viaSocket:
1. In a typical scenario, you will find Polling triggers of applications. For example, such as Notion, to trigger a workflow whenever a new item in the database is created.
.png)
2. At a regular interval of 15 mins, viaSocket sends API requests to the designated endpoints of the Notion, querying for updates or new data since the last query.
3. Upon receiving the API response, viaSocket processes the retrieved data, identifying any new orders or relevant changes.
4. Based on the processed data, viaSocket triggers the workflow that you set up, such as updating inventory records or sending order confirmation emails to customers.
More example:
Checking an RSS feed every 15 minutes for new blog posts and triggering an action when new content is detected.
Polling an e-commerce platform every hour to update inventory levels and trigger notifications when stock reaches a certain threshold.
Monitoring a social media account every 30 minutes for new mentions or messages and triggering automated responses.
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.
By understanding the nuances of Instant and Polling Triggers and how they interact with webhooks and APIs, businesses can harness the full potential of workflow automation to streamline operations and drive growth.
Polling Triggers
Apr 30, 2025Integrating viaSocket into your application boosts productivity and streamlines workflows. It connects your platform with over 5000 apps, offering seamless automation directly within your interface.
Key Benefits:
Seamless Integration: Users can access viaSocket's automation features without leaving your platform.
Extensive App Library: Automate workflows across a wide range of tools and services, including CRMs, project management apps, and email platforms.
Customization: Tailor the interface to match your app’s branding and provide a cohesive user experience.

How It Works:
Embed viaSocket: Use viaSocket’s Embed SDK to integrate workflow editors and trigger-action selections into your app.
Authenticate Users: Leverage OAuth 2.0 for secure authorization, enabling users to access their viaSocket accounts.
Manage Workflows: Users create and manage workflows—setting triggers and actions—from within your app’s interface.
Benefits for Users:
Enhanced Connectivity: Enable users to integrate and automate their favorite apps.
Example: Project management app users can sync files from Google Drive or Dropbox seamlessly.Streamlined Workflows: Automate repetitive tasks and reduce manual data entry.
Example: E-commerce users can automate order fulfillment with shipping carriers.Increased Productivity: Real-time data synchronization ensures efficiency without platform-switching.
Example: Sales CRM users can sync contacts with email marketing tools for smoother outreach.Customization Options: Users can tailor automation to their specific business needs.
Example: Task management users can trigger new tasks based on specific email conditions.Improved User Experience: Seamless workflows between apps eliminate silos, enhancing efficiency.
Example: Customer support users can manage tickets, CRM data, and communications in one place.
Embed viaSocket to create a unified, efficient, and scalable solution for your users.
Embed
Apr 30, 2025Creating multiple workflows often leads to situations where you need a similar workflow with minor adjustments. viaSocket offers a convenient solution, the ability to "duplicate a workflow".
This feature allows you to easily replicate a specific workflow within the same workspace or across different projects. With this handy feature, there's no need to recreate the same workflow repeatedly for minor modifications.

Duplicate flow
May 5, 2025A webhook is a real-time data notifier between applications. When an event happens in one app, it sends a signal to another app. In simple terms, it triggers a flow whenever a request hits its URL, sending data to viaSocket instantly.
Trigger Workflow with Webhooks :
Set Up Trigger: Create a new Workflow, select "Webhooks" to receive data from your app.
Get Webhook URL: viaSocket generates a unique URL. Copy it and add it to your app’s webhook settings.
Send Data to Webhook: Test by triggering your app to send data to the webhook. viaSocket will capture the data.
Map Data to Action: Choose the app you want to send data to. Map the webhook data to the app’s fields.
Now, viaSocket automates the data flow between your apps using webhooks.
Webhook as Trigger
May 5, 2025A multi-step workflow in viaSocket is a sequence of actions that are executed in a specific order to achieve a particular goal. These workflows are ideal for automating complex tasks that require several steps to be completed. Multi-step workflows can streamline processes, reduce errors, and improve efficiency by automating repetitive tasks. You can even change the order of these steps easily using the drag and drop feature of viaSocket.
Features of Multi-Step Workflow:
1. Sequential Execution:
Multi-Step workflows allow you to arrange actions in a specific order, ensuring that each step is executed sequentially.
2. Conditional Logic:
You can incorporate conditional logic, such as IF Conditions, to create dynamic workflows that respond to different conditions.
3. Monitoring and Tracking:
viaSocket offers monitoring tools called Logs and Metrics that allow you to track the progress of a multi-step workflow in real-time, view the status of each step, and identify any issues that may arise.
4. Customization:
Multi-Step workflows can be customized to suit your specific requirements, allowing you to tailor them to your unique workflow needs. You can add any third-party applications in the flow and can also change the order of these steps.
How to create a Multi-Step Workflow in viaSocket?
Identify the Steps: Start by identifying the individual steps involved in the workflow. Break down the task into smaller, manageable steps.
Arrange the Steps: Arrange the steps in the order in which they need to be executed. Consider dependencies between steps and any conditions that need to be met.
Test the Workflow: Before deploying the workflow, test it to ensure that each step is executed correctly and that the workflow as a whole produces the desired outcome.
Deploy the Workflow: Once the workflow has been tested, deploy it to automate the task.

Frequently Asked Questions:
Can I include conditional logic in a multi-step workflow?
Yes, you can include conditional logic, such as IF Conditions, in a multi-step workflow in viaSocket. This allows you to create dynamic workflows that respond to different conditions.
Can I delete any particular step in a multi-step workflow?
Yes, you can easily delete any step from the multi-step workflow by selecting the triple dot next to the step and then clicking the delete button.
How can I monitor the progress of a multi-step workflow?
viaSocket provides monitoring tools that allow you to track the progress of a multi-step workflow in real-time. You can view the status of each step, their execution time and the number of invocations involved.
Multi-Step Workflow
May 7, 2025The workflow automation in viaSocket relies on a Chip format for mapping data. Chips in viaSocket are placeholders that store and update data dynamically within the workflows. Think of them as containers that hold information such as text, numbers, or even more complex data structures.
Chips as Data Placeholders
Chips act as placeholders where you specify where you want to map data from API calls within a workflow. They provide a way to dynamically update and organize data received from APIs during the workflow process. Each chip represents a specific piece of data that will be filled in as the workflow progresses.
Mapping Data in Workflow
When setting up a workflow, you can designate where each piece of data from the API should be placed using these chips. This mapping ensures that data flows smoothly from one step to the next within the workflow, following the specified logic or rules.
For example, let's consider a scenario where a company uses workflow automation in viaSocket to manage employee onboarding. Information about the new employee is collected through an online form and stored in chips within the viaSocket.
Usage of Chips:
Each chip represents a specific piece of information about the employee, such as name, email, position, department, and start date.
These chips are mapped to corresponding fields in the company's employee database and other internal systems.
For example, the chip labeled "Employee Name" is mapped to the field for the employee's name in the HR database.
Similarly, the chip labeled "Department" is mapped to the department field in the company's organizational chart.
Dynamic Data Updates
As the workflow progresses and APIs start sending data, the chips dynamically update with the actual data received. This allows for real-time processing and manipulation of data within the workflow based on the information provided by the APIs.
For example, let's say you're using viaSocket to automate your sales process. You've set up a workflow where whenever a new lead is added to your CRM (Customer Relationship Management) system, an email is sent to the sales team.
Now, imagine you want to add a personal touch to the email by including the lead's name in the subject line. You can easily extract the lead's name from the data stored in the chip generated from the CRM API call. Then, you just have to insert this chip into the subject line of the email by simply clicking on Use it.
Now, every time a new lead is added to the CRM, the email subject line will dynamically include the lead's name, adding a personal touch to your communication.
Utilization Across Workflow Steps
The data captured in chips can be utilized across all steps of the workflow. This means that once data is mapped into a chip, it becomes available for use in subsequent steps or actions within the workflow.
In essence, chips serve as dynamic placeholders for data within workflows, enabling seamless integration and manipulation of data received from APIs across various steps of the workflow.
How to Map Data
Apr 30, 2025viaSocket allows you to integrate over thousands of apps for workflow automation. Custom Integrations in viaSocket empower users to create tailored workflows that meet their specific needs. If the app is not directly available in viaSocket, users can use the APIs or Webhooks to connect multiple apps.
With Custom Integrations viaSocket provides:
1. Enhanced Connectivity: Users gain access to a vast library of popular apps and services across various domains, such as project management, customer relationship management (CRM), communication, finance, and more. A variety of connectivity options are available from viaSocket, each specifically designed to satisfy different business needs.

2. Tailored Solutions: Custom Integrations give users the ability to integrate their own APIs in addition to the apps that are already available, allowing them to modify the platform to meet their unique needs. This feature is especially beneficial for individuals whose unique workflows or proprietary systems require custom integration with specialised tools or internal software solutions.
3. Scalability and Future-Readiness: The Custom Integrations feature offers a flexible integration framework that guarantees scalability and future-readiness as businesses grow and incorporate new technologies. Whether integrating with emerging apps or upgrading existing systems, users can easily create their own plug-ins using our inbuilt plug-in builder and can extend the platform's capabilities to meet evolving business requirements.
Custom Integrations isn't just a feature – it's a gateway to a world of endless possibilities. Whether you're streamlining your operations, automating tasks, or crafting your ideal workflow.
FAQs
Is there support available for Custom Integrations?
Yes, we provide comprehensive support for Custom Integrations. Our dedicated support team is available to assist you with setup, troubleshooting, optimization and any other questions or concerns you may have. Additionally, we offer resources to help you make the most of your integrations.
Custom Integrations
Apr 30, 2025Let say you have created a flow but you want to rearrange your step. Well, no worries, just click on the left side of your step, four dots will appear, hold it and just drag and drop it where you want to place it.
Just make the flow live and your sequence of flow execution steps get changed. Below you can see the drag button. So just hold that drag button and drag your step in the flow wherever you want.
In viaSocket, rearranging steps within your workflow offers several benefits:
With a simple click and drag, users can effortlessly adjust the sequence of steps in their workflow.
The ability to rearrange steps provides users with the flexibility to customize their workflow according to their specific requirements.
Users can quickly modify their workflow without the need for complex technical knowledge or extensive training.
Changes made to the workflow sequence are instantly reflected, allowing users to see the impact of their adjustments in real time.
By easily rearranging steps, users can optimize their workflow for efficiency, ensuring tasks are executed in the most logical order.
The intuitive drag-and-drop functionality promotes collaboration among team members, enabling them to easily communicate and coordinate changes to the workflow.