Blocker in Reels Workflow Setup – Need Suggestions

Community Support Request
1

Hi all,

We’re currently facing some blockers while setting up our Reels workflow. Below is the flow we’re trying to build:

  1. At the start, we accept a searchType.

  2. Using that searchType, we query the Master List table in MasterData to fetch the corresponding entityId.

  3. Once we have the entityId, we need to fetch the related table data that matches this entityId using api rule.

Issues we’re facing

  1. Accessing MasterData globally

    • Is there a way to get all MasterData details as a global reference in the workflow?

    • Currently, our planned approach is to make an API call to MasterData and then filter the results, but we’re not sure if this is the most efficient way.

  2. Dynamic URL mapping

    • We’re facing issues with dynamic URL mappings, which is leading to empty data responses.

    • Not sure if the issue is with how the URL parameters are being passed or how the workflow is handling dynamic mappings.

  3. Mapping API responses

    • We also need clarity on the best way to handle the mapping of API responses.

    • Specifically, how to structure the mapping logic so that the workflow correctly transforms and consumes the API data (instead of ending up with missing or empty fields).

What we need help with

  • Suggestions on the best approach to structure this workflow.

  • Best practices to handle global MasterData access without repeatedly calling APIs (if possible).

  • How to properly implement dynamic URL mapping in this kind of flow.

  • Recommended patterns for API response mapping in workflows.

1 Like
2

@Sam @Rocky Please help

1 Like
4

@Athul- Please let me know when we can connect, as I have some doubts regarding the questions you raised.