Custom Variables act as versatile containers within viaSocket, capable of holding various types of information essential for your workflows.

Custom Variables allow you to tailor your workflows precisely to your requirements. Gone are the days of one-size-fits-all automation – now, you can dive deep into the inner workings of your workflows and mold them to perfection.

Custom Variables allow users to create and initialize variables within their workflows using JavaScript. These variables can hold various types of data, such as text strings, numbers, or even complex objects. Once defined, these variables become accessible and usable across your entire workflow.

Step by step guide on how to use custom variables in viaSocket

1. You can add a variable and use it across the workflow with the help of "Custom Logic (AI)."

2. Simply tell the AI your requirement, such as the type of variable you need and its name. It will create the variable for you and ensure it's set up correctly.

The "Function" in viaSocket is a powerful tool designed to enhance customization within your workflows. It allows users to create custom JavaScript functions that can be seamlessly integrated between any steps of their workflows. This feature empowers users to tailor their automation processes precisely to their needs, adding flexibility and efficiency to their workflows.

Key Benefits:

• High-Level Customization: With the "Function" feature, users have the ability to create custom functions tailored to their specific requirements. This enables them to address unique use cases and handle complex scenarios with ease.

• Flexibility: Users can insert custom functions at any point within their workflow, allowing for dynamic control over the flow of data and actions. This flexibility ensures that workflows can adapt to changing requirements and diverse integration scenarios.

• Enhanced Automation: By leveraging custom JavaScript functions, users can automate repetitive tasks more effectively. These functions can perform intricate operations, manipulate data, and interact with various applications and services, streamlining processes and improving productivity.

How it Works:

1. There are two ways to add your custom JS code

   —> Write it your own

   —> If you'd like AI to write code for you then in the dialog box, enter a prompt that describes your desired code. Click Test, then click Save. 

2. Once you've finished adding your code, click Continue to test your code step. If your code is valid, the step will show it was successful and display the data. 

   Use code steps to power your business's growth

   With Code by viaSocket, you can customize your workflows so they automate complex tasks, integrate seamlessly with any API or custom application, and ultimately, solve problems unique to your business. 

   By adding that extra layer of code, you can transform your data in ways standard integrations can't.

The Multiple Paths feature in viaSocket allows you to split your workflow into different paths, with each path performing specific actions based on the conditions you set. You can define these conditions using operators like "less than" or "greater than," giving you full control over how your data moves through the workflow and ensuring that different actions are triggered depending on the criteria you’ve defined.

For example: If event A occurs in your trigger app, act X. But if event B happens, act Y instead.

How to get started with Multiple Paths

Step 1: Once logged into viaSocket, navigate to the workflow editor.

Step 2: In the workflow editor, search for and select your trigger app. Connect your account, configure the trigger step, and test it to ensure it's working properly.

Step 3: Next, add an action to your workflow, and select the “Multiple Paths” feature from the built-in tools to create different routes based on your conditions.

Step 4: Create path branches and define specific conditions for each branch. Based on these conditions, the data will follow the appropriate path, ensuring the right actions are taken for each scenario.

Step 5: Test your paths.

Step 6: Now, add actions to each path, just as you would in any workflow, ensuring they match the conditions for each branch.

Step 7: Once you've finished adding your paths and actions, be sure to test the workflow and publish it to start running.

Example of Using Multiple Paths

If you send personalized messages whenever their status changes in your CRM. Then in that scenario, you can use multiple paths like this : 

When a customer's status updates in your CRM, you can set up two paths:

In Path A, if the status is exactly "new customer," send a personalized welcome message. In Path B, if the status is "inactive," send a re-engagement message to encourage them to return.

Importance of using Multiple Paths in your Workflow

1. Personalization: Set different actions for different conditions.

2. Efficiency: Automate tasks for various situations in one workflow.

3. Flexibility: Handle multiple scenarios based on the trigger.

4. Simplicity: Combine actions into one workflow instead of creating many

Delay is an in-built tool in viaSocket that helps you pause your workflows for a specified amount of time before the next actions take place.

This feature is perfect for scheduling tasks on your timeline, such as sending follow-up emails, creating reminders for incomplete tasks, or triggering automated actions at just the right moment. Whether you need to space out notifications or implement timed responses, Delay keeps your workflow organized and in sync with your goals.

Why Do We Need Delay in a Workflow?

Imagine you run an e-commerce store and use a workflow to send a thank-you email after a purchase. However, bombarding your customer with promotional emails immediately after the thank-you note could feel intrusive.

Without Delay:

1. The customer completes their purchase.

2. The thank-you email and promotional emails are sent simultaneously.

3. The customer might feel overwhelmed, leading to email fatigue.

With Delay:

1. The customer completes their purchase.

2. The thank-you email is sent instantly to acknowledge the transaction.

3. A Delay of 2 days is added to the workflow.

4. The promotional email about complementary products or discounts is sent, arriving at the right moment when the customer is likely to consider another purchase.

This timing improves the customer experience, nurtures the relationship, and increases the chances of a successful upsell or re-engagement.

Delays are similarly useful in scenarios like:

• Scheduling reminders for incomplete tasks.

• Spacing out notifications to prevent interruptions.

• Automating birthday or anniversary greetings at the exact time.

By adding Delay to workflows, you can create more thoughtful, effective, and user-friendly automation.

Will Delays Impact Execution Time Limit of the Workflow?

No, adding a delay does not affect the total execution time of your workflow in terms of processing capacity. Delays are simply pauses inserted between steps to control when the next action should run. These pauses do not consume additional resources or extend the overall processing duration counted towards your workflow limits.

For example, if your workflow includes a 2-hour delay before sending a follow-up email, those 2 hours are not considered "active" execution time. The system is merely waiting during that period, and the actual execution resumes when the delay ends.

This ensures that delays help you time your tasks effectively without impacting the efficiency or limits of your workflow's processing.

How to get started with Delay

Step 1 : Once logged into viaSocket, navigate to the workflow editor.

Step 2 : In the workflow editor, search for and select your trigger app. Connect your account, configure the trigger step, and test it to ensure it's working properly.

Step 3 : Next, add an action to your workflow, and select the “Delay” feature from the built in tools.

Step 4: Enter the time limit in seconds, minutes, hours, or days by following the format suggested in the field's placeholder.

Step 5 : Define the actions to be executed after the delay, then test and publish the workflow.

Can I track the delay times in my workflow logs?

Yes, you can track the delay times in your workflow logs. The logs will include detailed information about the duration of each delay, offering full transparency regarding the time spent in waiting periods. 

This allows you to monitor the workflow’s progress, understand any pauses, and ensure everything is running as expected. You can easily review the timeline to see how long each step takes, including delays, and identify any areas that may need optimization for better efficiency.

Add a comment in your steps and know what is happening

You can add comments anywhere in between the flow to remind or clarify something. Comment block is present for your understanding, meaning if you want to give some instructions to use a flow or to remind something then you can put a comment there to see what we have to do. 

You can write anything inside the comment, there is no word limit or restriction inside the comment.

Benefits of adding comments in your workflow

1. Users can easily share insights, clarifications, and instructions on each step, improving teamwork.

2. Comments provide clear explanations for each step, making workflows easier to understand for all team members.

3. Centralized discussions within viaSocket reduce the need for external communication channels, keeping all relevant discussions organized alongside the workflow.

In workflows, human approval is sometimes necessary for making accurate decisions. That's why viaSocket offers the "Human Intervention" feature, allowing you to manually step in at critical points without worrying about time limits, as the workflow is paused. When approval is needed, the workflow waits until you give the go-ahead, after which it continues with the remaining steps. This ensures thoughtful decision-making and improves the effectiveness of your automation.

Why Do We Need Human Intervention in a Workflow?

Let’s understand the necessity with the example: An employee submits an expense report for travel reimbursement through the company’s finance system. If the expense exceeds a certain threshold (e.g., $1,000), it triggers human intervention. At this point, the system pauses and sends a notification to the manager or approver, asking for review and approval.

• If Approved: Once the manager approves the report, the system resumes processing. The payment request is sent to the finance department, and the employee is reimbursed.

• If Denied: If the manager denies the report, the workflow sends a notification back to the employee to revise or provide additional information.

Execution Time Calculation

In the case of human intervention in workflows, it is essential to understand how the execution time limit is calculated. When human intervention occurs, the execution flow pauses and the time counting stops, while logs are generated for the actions executed up to that point. Once approval is received from the human side, the time counting resumes, and the workflow continues until completion. This ensures that the time spent waiting for human action is excluded from the overall execution time.

How to get started with Human Intervention

Step 1: Once logged into viaSocket, navigate to the workflow editor.

Step 2: In the workflow editor, search for and select your trigger app. Connect your account, configure the trigger step, and test it to ensure it's working properly.

Step 3: Next, add an action to your workflow, and select the “Human Intervention” feature from the built-in tools.

Step 4: Choose any one of the interaction services.

Step 5 : Define buttons for seamless interaction, and map each button to the required values for accurate condition checks.

Step 6: Now, define the further actions that are executed only after receiving human approval.

Step 7: Test and publish the workflow.

Importance of Human Intervention in Workflow

1. Decision-Making: It allows for nuanced judgment that automated systems cannot provide.

2. Quality Control: Humans can identify errors and ensure high standards.

3. Flexibility: Human involvement enables real-time adjustments to changing circumstances.

4. Complex Problem Solving: Humans can think critically and creatively to solve intricate issues.

5. Emotional Intelligence: Human interaction brings empathy and understanding to tasks.

The Memory tool in viaSocket is designed to store data across workflow runs, enabling seamless data sharing and connection between different steps or runs. This tool provides a persistent storage solution, making it easier to maintain context and continuity in your workflows.

Key Features

• Persistent Storage: Retain data beyond the execution of individual workflows.

• Data Sharing: Facilitate the exchange of data between multiple workflow steps or even separate workflows.

• Scalability: Handle diverse data sizes and types, ensuring robust functionality for all use cases.

• Flexibility: Retrieve, update, or clear stored data based on workflow requirements.

Supported Data Types

The Memory tool supports two types of data formats:

• Dictionary

• JSON

Supported Actions

Within the Memory tool, you can perform the following actions:

1. Create or Update Record: Add new data or modify existing data seamlessly. Use this action to ensure your workflow data stays updated and relevant.

2. Update a Record by ID: Modify specific records using the Update by ID action. This allows you to directly update a particular entry in your MongoDB storage by its unique identifier, ensuring precise changes to your stored data.

3. Find Record: Effortlessly access stored data with the Read action. Retrieve any saved information at any point in your flow to support decision-making and trigger subsequent actions based on the retrieved data.

4. Delete Record by ID: Maintain an organized and efficient workflow by removing unnecessary data with the Delete action. This allows you to securely delete obsolete records, optimizing your storage for active and relevant information.

5. Add New Record: Store new data seamlessly within your workflow using the Create action. Whether you're saving configurations, flags, or other crucial information, this action securely adds data to your MongoDB-based storage, ready for use in your automation flow.

6. Update Record Using Filter: Refine your updates by applying filters to target specific records. This action enables you to make precise modifications based on conditions you define, enhancing the flexibility of your data management.

Use Cases

1. Session Management: Store user session information and maintain it across different workflow runs.

2. Data Continuity: Keep track of intermediate results or process states to use in subsequent steps.

3. Conditional Logic: Use stored data to determine workflow paths or trigger specific actions.

4. State Management: Manage states in workflows that require a multi-step process with dependencies.