Recommendations for incorporating static data that doesn't change



  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Dave Guderian is it a list of ids and you need to grab the correct id for a given source value? Or is it just a single id value you need to use? If the latter, it sounds like you could utilize integration, flow, flow grouping, import, export, or connection settings. Under each of these resource types, there is a section called "custom" and under it you can place static data and reference it just about anywhere within a flow.


    If you want to take it one step further, you could actually build out a form within that custom settings so that you don't edit raw JSON each time and instead interact with a text, integer, etc field type.


    If you need the former (list of ids to look up against), you could store an array of values in settings and then utilize an {{each}} handlebar expression or a script. Additionally, you could utilize a state via the state api, but that would be a bit more complex and maybe overkill for this situation.

  • Nate Briant Senior Solutions Consultant
    Celigo University Level 4: Legendary
    Great Answer

    Hi David,

    You can add static data via the mapping in the form of hard coding data in the mapping which works best for single values or by creating a Static Value to Value mapping which is like a table that returns a value based on the input but is static in its values.

    Under the mappings, you can click the gear icon shown in the screenshot below which will give you the mapping options.

    You can then select lookup, Static: Value to Value which will allow you to create the lookup table in which you can store your static values.  It will return the import field value based on the export value so in the screenshot included the input could be pineapple and it would map yellow.


    Let me know if this helps!


Please sign in to leave a comment.