Instant Trigger runs your workflow immediately when something happens in your app.
👉 No delay
👉 Real-time execution
How it works
Your app sends data when an event happens
viaSocket receives it
Workflow starts instantly
Examples
New order → send confirmation email
New lead → notify team
Form submitted → save data
Ticket created → assign and notify
⚙️ Quick Setup
1. Subscribe
👉 This tells your app to start sending webhook data to viaSocket
What you do:
Add API details to register the webhook
Pass the webhook URL from viaSocket
What you need to do
When your API asks for a webhook URL:
👉 Use this value:
context.inputData.hookUrlWhat this does
viaSocket generates a webhook URL
This value sends that URL to your app
Your app starts sending data to viaSocket automatically
👉 After this, your app knows where to send data
2. Sample Data (Perform List)
👉 Used to fetch sample data for testing
What you do:
Call an API that returns example data
Helps you preview what data will look like
👉 This is important for mapping fields correctly
3. Perform (Modify data before sending on flow)
👉 Used to clean or modify data before passing it forward
What you do:
Format response
Remove unwanted fields
Adjust structure if needed
👉 Optional, but useful for cleaner workflows
4. Unsubscribe
👉 Stops your app from sending webhook data
What you do:
Add API to remove webhook subscription
👉 Used when user disconnects or disables trigger
5. Transfer Data (Optional)
What it is
Transfer Data allows you to use existing (historical) data instead of only new events.
What it means in simple terms
Normally:
👉 Trigger runs → only new data is processed
With Transfer:
👉 You can also use past data that already exists
What it does
Lets you run workflows on old data
Enables bulk processing
Useful for data migration or syncing
When to use this
You want to process existing records
You need bulk operations
You are migrating or syncing data
💡 Simple Flow
👉 Subscribe → Receive data → (Optional modify) → Send to workflow
Best Practices
Always test with real sample data using the Perform List API
Use unique webhook URLs per user when supported
Secure your webhook with auth headers or signature validation
Monitor the logs tab in viaSocket to debug incoming payloads