The inbuilt tools of viaSocket enhance your workflows by enabling advanced logic, data manipulation, and customization, ensuring smooth and efficient integrations tailored to your needs.

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

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.

Our primary dashboard is dedicated to organization management, providing a centralized hub for creating and overseeing individual organizations.

The significance of an organization lies in its ability to allow users to administer members with access permissions, create distinct organizations for specific workflows, and determine whether these organizations should be public or private to restrict access.

To illustrate, envision organizations as entities similar to your company, such as a firm, school, or college, where the entire entity represents an organization.

Each organization can be treated independently, much like how you would manage distinct firms or institutions. In viaSocket, akin to managing practical organizations, you need to handle each organization separately. 

Steps to Follow:

Creating a new organization is easily accomplished by selecting the "create new org+" button, and users have the flexibility to establish multiple organizations tailored to their requirements.

​

Metrics in viaSocket are measurements that track the performance of your workflows. They provide important data on how well your workflows are running, helping you identify areas for improvement. Metrics help you monitor things like execution time, success rates, and errors.

Flow Wise & Step Wise Metrics

Metrics provide quantitative data about how well your workflows are performing. They track parameters such as execution time and status for each and every step of a workflow, allowing you to assess the efficiency of your automation processes.

Flow Wise Metrics
Flow Wise metrics give you an overview of the performance of the entire workflow. They show you the combined data for all steps within a flow, helping you track:

• Overall execution time for the entire workflow.

• Success rate and error rate for the whole flow.

These metrics give you a broad picture of how your workflow is performing.

Stepwise Metrics
Stepwise metrics focus on the performance of individual steps within your workflow. This allows you to see:

• Execution time for each specific step.

• Error rate or success rate for each step.

Stepwise metrics help you pinpoint which specific steps are performing well and which might need improvement.

Viewing Metrics in viaSocket

viaSocket presents these metrics in chart form, which makes it easy to visualise the data. You can view:

• Bar charts to compare the performance of different workflows or steps.

• Line charts to track performance over time (like changes in success rate or execution time.

Security and compliance are paramount considerations for viaSocket, ensuring the protection of user data and adherence to regulatory requirements such as GDPR (General Data Protection Regulation).

Here's how viaSocket maintains a high level of security and compliance:

Data Encryption

viaSocket employs robust encryption techniques to secure data both in transit and at rest. This ensures that sensitive information remains protected from unauthorized access or interception.

Access Control

viaSocket implements strict access control mechanisms to restrict access to user data. Access is granted only to authorized personnel who require it for legitimate purposes, reducing the risk of unauthorized data breaches.

GDPR Compliance

viaSocket complies with GDPR regulations, which are designed to safeguard the privacy and personal data of individuals. This includes obtaining explicit consent for data processing, providing users with access to their data, and implementing measures to ensure data security and integrity.

Data Minimization

viaSocket follows the principle of data minimization, collecting and processing only the minimum amount of data necessary to fulfill its intended purpose. This reduces the risk of data exposure and helps maintain user privacy.

Regular Audits and Assessments

viaSocket conducts regular security audits and assessments to identify and address potential vulnerabilities or compliance issues. This proactive approach helps ensure that security measures remain effective and up-to-date.

Secure Infrastructure

viaSocket utilizes secure infrastructure and hosting providers to maintain the integrity and confidentiality of user data. This includes implementing firewalls, intrusion detection systems, and other security measures to protect against external threats.

Data Processing Agreements

viaSocket establishes data processing agreements with its users, outlining the responsibilities and obligations of both parties regarding the handling of personal data. These agreements help ensure transparency and accountability in data processing activities.

Overall, viaSocket prioritizes the security and privacy of user data, adhering to stringent security standards and regulatory requirements such as GDPR. By implementing robust security measures and compliance practices, viaSocket provides users with confidence in the protection of their data.

Triggers kick off the entire 

Automation

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

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

Notion

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.

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.

Integrating 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:

1. Embed viaSocket: Use

   viaSocket’s Embed SDK

   to integrate workflow editors and trigger-action selections into your app.

2. Authenticate Users: Leverage OAuth 2.0 for secure authorization, enabling users to access their viaSocket accounts.

3. Manage Workflows: Users create and manage workflows—setting triggers and actions—from within your app’s interface.

Benefits for Users:

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

2. Streamlined Workflows: Automate repetitive tasks and reduce manual data entry.
   Example: E-commerce users can automate order fulfillment with shipping carriers.

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

4. Customization Options: Users can tailor automation to their specific business needs.
   Example: Task management users can trigger new tasks based on specific email conditions.

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

Creating 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

projects

A

webhook

Trigger Workflow with Webhooks :

1. Set Up Trigger: Create a new Workflow, select "Webhooks" to receive data from your app.

   

2. Get Webhook URL: viaSocket generates a unique URL. Copy it and add it to your app’s webhook settings.

3. Send Data to Webhook: Test by triggering your app to send data to the webhook. viaSocket will capture the data.

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

Pause Workflows:

• Pausing a workflow allows you to temporarily stop its execution without deleting or altering its configuration. This can be useful when you need to investigate an issue, perform maintenance, or make adjustments.

• Pausing a workflow can help mitigate risks during critical periods or when unexpected issues arise. It gives you time to assess the situation and take appropriate actions without impacting ongoing operations.

Share Workflows:

• Share as Templates: If you have a workflow that you think others might find useful, you can share it as a template. This allows others to use your workflow as a starting point, saving them time and effort.

• Move to Another Folder: To keep things organized, you can move your workflow from one folder to another. This is especially helpful when you have multiple workflows and need to sort them based on categories or tasks.

• Duplicate Your Flow: Sometimes, you may want to make changes to a workflow without affecting the original. You can duplicate your flow, creating an identical copy that you can edit freely while keeping the original intact.

Delete Workflows:

• Temporarily remove workflows from active use without permanently deleting them.

• Clean up your workspace by moving unused or outdated workflows to trash.

• Provides a safety net in case you need to restore a workflow later.

In viaSocket, handling workflows is really easy. You can keep an eye on how your workflow is doing by looking at its history. You'll see the history option on the left side of the flow. Clicking on a specific time shows you what happened at that time. Each step in the flow will display the data from that moment.

This helps you see if it's working well, if the data is right, and if anything gets lost, you can find it in the history.

Here's why keeping track of your workflow's history is super handy

1. Checking if it Works: You can see if your workflow is doing its job by looking at when it runs. 

2. Getting the Right Stuff: You can make sure the data going in and out is correct.

3. Finding Problems: If something's wrong, you can spot it fast. 

4. Saving Lost Data: If data gets lost, you can go back to an earlier run to get it back.

📌 For example, if one day leads don't show up in your CRM, you can check the history to see what went wrong. Then, you can go back to the previous day's records to get those leads back. Easy fix!

A 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

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

3. Monitoring and Tracking: 

viaSocket offers monitoring tools called 

Logs

Metrics

4. Customization: 

Multi-Step workflows can be

customized

How to create a Multi-Step Workflow in viaSocket?

1. Identify the Steps: Start by identifying the individual steps involved in the workflow. Break down the task into smaller, manageable steps.

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

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

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

Error handling in viaSocket involves the detection and management of errors that occur during the execution of workflow steps.

Detection of Errors

viaSocket detects errors that occur during the execution of a workflow step. These errors could be due to various reasons such as invalid input data, network issues, or API failures.

📌 For example, if a workflow encounters an error while attempting to retrieve data from an external API, viaSocket will detect the error and initiate the error handling process.

​

Skipping of Dependent Steps

Upon detecting an error in a step, viaSocket skips that particular step and any subsequent steps that depend on the data generated or processed by the erroneous step. This prevents the propagation of errors to downstream steps and ensures that the workflow continues to execute without being blocked by the error.

Execution of Independent Steps

viaSocket continues to execute other steps in the workflow that are not dependent on the data from the erroneous step. This allows the workflow to progress and perform other tasks that can be executed successfully despite the error.

By handling errors in this manner, viaSocket ensures that workflows can gracefully recover from errors and continue to execute efficiently.

How to Publish a Flow in viaSocket

Publishing your flow in viaSocket is quick and easy. Follow these steps:

1. Create and Save Your Flow
   First, create your flow and make sure to save it. After saving, test your flow to ensure everything is working as expected.

2. Find the Publish Button
   Once your flow is ready, look for the Publish button in the top-right corner of the screen. This is where you can publish your flow.

3. Add a Name and Description
   You will be prompted to enter a name and description for your flow. If you don't provide a description, the AI will generate one for you automatically.

4. Click Publish
   After adding the name and description (or letting the AI handle it), click Publish. Your flow will now be live and available for use.
   
   

The 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

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.

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.

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.

viaSocket allows you to integrate over 

thousands of apps

Webhooks

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

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.

When building automations in viaSocket with database applications like

Google Sheets

Airtable

To support bulk data processing, backfilling, or migrating existing records, viaSocket provides an optional step immediately after publishing your flow: Run the flow on historical data.

When to Use This

Typical scenarios include:

• Bulk transfer of existing records from one system to another.

• Reprocessing older rows with updated workflow logic.

• Migrating data from legacy apps using a newly built automation.

• Testing workflows with a real data batch before going live.

How It Works

1. Configure the Flow

• Set up your flow in viaSocket with the appropriate steps.

• Use "New Row Created" as the trigger, connecting your data source (Google Sheets, Airtable, etc.).

2. Publish the Flow

• Click Publish once the flow is ready.

3. Prompt to Run on Historical Data

• After publishing, a confirmation prompt will appear:

  "Do you want to run this flow for historical data?"

• Choose Yes to continue.

Selecting and Running Historical Data

Once confirmed, a dedicated interface opens where you can view and manage the historical data:

Data View

• A structured table will show all existing rows from the connected data source.

• Each row corresponds to a potential trigger input for the flow.

Actions Available

• Filter rows by specific column values.

• Sort rows by any column.

• Select individual or multiple rows.

Execution

• Once selection is complete, click Run Flow.

• The system will execute your flow for each selected row, processing the data through the same steps defined in the automation.

• All executions are recorded and visible in Flow

  History

  .

With viaSocket's step on/off button feature, you can precisely manage your automation workflows by turning specific steps on or off within your actions.

When a trigger is activated, the workflow executes according to the enabled steps, allowing real-time customization. This flexibility ensures your workflows remain efficient and responsive without the need to remove or recreate steps.

Understanding Step Status in viaSocket Workflows

In viaSocket, each step within a workflow can exist in one of two states:

1. On: When a step is turned on, viaSocket actively executes that step whenever the workflow is triggered. The step will check for new data and perform its designated action(s) as part of the overall workflow.

2. Off: Steps that are turned off do not perform actions or check for new data within the workflow. We might turn off a step under specific conditions:

   • If you’re temporarily pausing a specific part of the workflow while testing or debugging other steps.

   • If you need to prevent a particular action from executing due to changes in your process or temporary suspension of that action.

   • If a step is no longer relevant to the current workflow but might be needed again in the future, allowing you to keep the step available without deleting it.

By managing the status of each step, you can fine-tune your workflows in viaSocket, ensuring that only the necessary steps are active and that your processes remain flexible and adaptable.

Key Benefits

The step on/off button feature in viaSocket provides several significant benefits:

1. Precise Control: Fine-tune your automation by toggling individual steps on or off, controlling their execution.

2. Flexible Adjustments: Adapt workflows to changing needs by pausing or reactivating steps without reconfiguration.

3. Efficient Testing: Test and debug specific steps without disrupting the entire workflow for faster issue resolution.

4. Optimized Performance: Enhance efficiency by running only relevant steps, streamlining operations and improving performance.

With viaSocket’s step on/off button feature, you can effortlessly manage and optimize your workflows, ensuring they adapt seamlessly to your needs. This flexibility enhances efficiency and allows for precise control over your automation processes.

viaSocket incorporates a scheduling feature called Cron, allowing users to automate their workflows at specific times, dates, or days. Suppose you want to run your workflow after every particular interval of time so you can use Cron there. For instance, users can set up a Cron to execute a workflow every day at 10 am from Monday to Friday.

Steps to create a Cron

For instance, we will create a workflow that will send an automated message on Slack at user specific time. 

Step by step guide on how to create Scheduled workflows.

1) Create a new workflow and opt for the Cron option.

2) Enter a simple English phrase that specifies both when and how often you want the trigger to occur.

For example, every Monday at 10 AM.

3) This scheduling functionality streamlines the process of automating tasks according to specified timeframes and by doing so, every Monday at 10 AM, a message will be sent to the slack channel specified by user. 

4) You can specify cron like every minute, every 2 hours, every week etc. So, your workflow automatically executes after that time. For making cron active you have to click "Make Live" your flow. 

Cron can run your flow automatically after a given time. If you are applying a cron then you don't have to use a webhook to hit your flow.

📌 Examples of cron scheduling: 

Every Day at Noon: Every day at 12:00 PM

Every Monday Morning: Every Monday at 9:00 AM

Every Hour: Every 30 Minutes

Every Midnight on Fridays: Every Friday at 12:00 AM

These examples showcase simple Cron expressions for scheduling tasks at different intervals, days, and times. You can adjust the expressions based on your specific scheduling needs within viaSocket.

Let 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

Looping is a powerful feature that allows you to repeatedly run a specific action or set of actions for each item in a list. This ensures that each item is handled individually and consistently, which is especially useful when dealing with multiple data points or records.

Example:

Imagine you have a list of customer orders. Each order needs to go through the following steps:

1. Send a confirmation email.

2. Update the order status.

3. Notify the customer.

Looping ensures that each order is processed individually and in the correct sequence.

How to add loop in workflow

To implement looping in a workflow, you can utilize Webhook Advanced Configuration. This allows you to iterate over a list of items and run actions for each item individually.

Steps to Implement Looping in a Workflow:

1. Hit Flow Individually:

   • If your payload contains a list, and you want to run the flow for each item individually, enable the Run flow one by one option. This ensures that the flow processes each item separately.

   Note: This option is limited to a maximum of 1000 items in the list.

2. Set Up Delay:

   • You can introduce a delay between each execution of the flow. This is useful if you need to space out the actions and avoid overloading your system.

   • Use the delay parameter in the query string to set the time between each flow execution in minutes.

   Example:
   https://flow.sokt.io/func/scriRofnax1Z?delay=2
   This setup will introduce a 2-minute delay between each flow execution. Adjust the delay time according to your needs.

   Important: After setting the delay, the flow will wait for the specified time before processing the next item.

3. Flow Control Condition:

   • You can set a condition that determines whether the flow should run, based on certain criteria. This condition can be a logical expression, such as checking if a field or parameter in the payload meets a specific value (e.g., if a field is non-empty).

   Example:

   • Enable a condition like "only run the flow if a field contains a valid value." This ensures the flow only runs when the conditions are met.

Examples of Looping in Workflow Automation

1. Sending Notifications to Multiple Users

• Data: A list of users who need to be notified (e.g., new leads, updates, etc.).

• Loop: The workflow loops through each user.

• Action: For each user, it sends a personalized notification via email, SMS, or push notification.

2. Updating Records in a Database

• Data: A list of database records that need to be updated.

• Loop: The workflow iterates over each record.

• Action: It performs actions like updating a field, adding a note, or tagging the record based on certain conditions.