feat(flows): map javascript json paths to custom fields - #1136
Open
JuanBifrost wants to merge 1 commit into
Open
feat(flows): map javascript json paths to custom fields#1136JuanBifrost wants to merge 1 commit into
JuanBifrost wants to merge 1 commit into
Conversation
Let Execute JavaScript use the same JSON-path picker as External API Request so any returned object can fill any custom fields the author chooses. Co-authored-by: JuanBifrost <JuanBifrost@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Execute JavaScript can map any JSON path from the returned value onto any custom field, using the same “Pick JSON path” picker as External API Request. An optional dump field still stores the full return value.
Existing steps that only set
customFieldIdkeep working (mappingdefaults to[]).Tested in production: split a stored
lat,lngGPS string into two custom fields from one JS step.How to test
return { latitude, longitude }.returnstill requires the dump/output field.Screenshots
Builder: JSON path rows (
latitude/longitude→ custom fields). The optional “full JSON output” field can stay empty:WhatsApp: after the location pin, JS writes the two fields and the flow echoes them (
lat/lon). The native “Send location” button is from a separate Get User Data change, not this PR: