How to Map Data

Data Mapping in viaSocket is how you connect data between different steps in your workflow — from triggers, actions, or even custom JS code.

You don’t need to create variables or placeholders manually. viaSocket automatically makes data from one step available to all the steps that follow.

Think of it like passing data along a chain: one step produces data, and the next step decides how to use it.

🪜 Step-by-Step: How to Map Data

Step 1: Set Up a Trigger Step

Start by adding your trigger — for example, “New Form Submission” or “New Record in CRM.”

• Connect your app and test the step to fetch sample data.

• viaSocket will show all available fields you can use later (like name, email, or ID).

Step 2: Add the Next Step

Add an action step, Custom API, or JS Code block.
When you open the configuration screen, click into any field — viaSocket will display data from all previous steps in a dropdown (chips view).

Step 3: Map Data Fields

Click on a field and select the chip (data token) you want to map.

• Example: Use {{email}} from your form trigger in the “Recipient Mail” field of your email step.

• Example: Use {{formatted_date}} from a JS code step to fill a timestamp field.

Each time your workflow runs, viaSocket replaces these chips with real data from that specific run.

Step 4: Combine Data from Multiple Steps

You can use chips from multiple previous steps in the same field or body.

• Combine a user’s name from Step 1 and a discount code from Step 3 in an email template.

• Merge an API response field with a processed value from JS Code.
  

  

Step 5: Test Your Workflow

Run a Test to confirm that mapped data is appearing correctly.

Check that all placeholders are replaced with live data.
If a field looks empty, recheck the mapping or test output of the earlier step.

Step 6: Activate the Workflow

Once you’re satisfied, click Set Live.
viaSocket automatically keeps data flowing across all connected steps — no manual setup needed.

Summary

Data Mapping in viaSocket makes it effortless to pass data between triggers, actions, and code.
Each step automatically shares its output downstream, so you can visually map values without writing any code.