Built with DocStarIn viaSocket, a task refers to one complete execution of a workflow. Each time a workflow is triggered—whether by an app event, webhook, or scheduled run—it counts as one task.
When does a task happen?
An task occurs when a workflow is triggered by any of the following:
App Integration Trigger – e.g., a new lead created in HubSpot.
Webhook Trigger – e.g., an external system sends a POST request to your viaSocket webhook URL.
Scheduler (Cron) Trigger – e.g., a workflow set to run every morning at 9 AM.
Regardless of how many steps your workflow has, it counts as one task when triggered.
Example
Suppose you have a workflow:
Trigger: New submission in Typeform
Step 1: Fetch user details from your CRM
Step 2: Send WhatsApp via MSG91
Step 3: Log data in Google Sheets
Each time a new submission is received, the entire flow runs once. That is one task.
Execution time limit
Every task in viaSocket has a 30-second execution time limit by default.
If your workflow completes within this limit, it counts as one task.
If the execution exceeds 30 seconds, another task will be counted automatically.
Need more time per task? Execution time limits can be increased. Talk to sales to learn more.
Frequently asked questions
What happens if my workflow exceeds the 30-second execution limit?
You’ll be charged one additional task for every 30 seconds of execution time used. You can optimize steps or reach out to increase the time limit.
Are manual tests or step previews counted as task?
No, testing individual steps during workflow creation or setup does not consume task quota.
How can I track my task usage?
You can view your usage inside your viaSocket dashboard under Settings → Usage. It gives you a breakdown of total tasks and which workflows are consuming them.
Is there a cap on the number of steps in a workflow?
There’s no hard limit on the number of steps, but more steps may increase execution time. Keep performance in mind as you scale your automation.
