Skip to main content

Data Mapper now available in HTTP Action bodies

  • January 26, 2026
  • 1 reply
  • 14 views

Kevin Mok
Forum|alt.badge.img+1

You can now use Data Mapper syntax directly in HTTP Action bodies.

If you've built complex HTTP Actions with Mustache, you know the pain:

  • Triple curly braces `{{{variable}}}` for everything
  • Passing arrays? Hope you remembered `$STRINGIFY_JSON()` in your Compound Action first
  • Formatting data in one place, using it in another — inconsistent and confusing
  • Want conditional fields? Good luck wiring that through Mustache

The experience was fragmented. You'd write transformation logic in your Compound Action, stringify everything, then pray it landed correctly in the HTTP body.

Not anymore.

What you can do now:

# Build a list of objects from input data
updates:
MAP():
items: items
converter:
item_id: item.id
item_name: item.name.$UPPER()
qty: item.quantity

→ Filter arrays before sending  
→ Conditionally include fields  
→ Transform 2D arrays into structured JSON  
→ Use DSL expressions for string manipulation and type conversion  
 

Docs: Data Mapper in HTTP Actions

This is great for bulk updates, complex API integrations, and any situation where you need more than simple variable substitution.

 

Big thanks to Avi Nayak ​(@anayak)  for driving this and the Eng team for shipping it. 🙌

If you're building plugins with complex payloads, give it a try and let us know how it goes.

1 reply

rgeroulo
Forum|alt.badge.img
  • Employee
  • January 26, 2026

This will be super useful for building Outlook or GCal Book Meeting use cases.

No more getting a list of users, running a script to loop through the list and create the correct json, then piping that into the Outlook/GCal Book Meeting action.

Now we can remove the script and do the transformation directly in the HTTP Action body!!