Question:
In our platform, we have currently embedded the connection widget from Workato, which allows users to configure connections for Workato connectors.
Current workflow:
Users configure the required connector connection via the connection widget.
They select a recipe to execute from our platform.
When they start the evidence collection process, our platform triggers the selected recipe using a webhook trigger.
The recipe then executes, fetches the evidence, and pushes it back into our platform.
So far, users are only able to configure connections. Now, we want to enable users to also configure action input parameters.
We have reviewed the
Workato embedding documentation . While full embedding is an option, we do not want to expose our users to the complete Workato interface, since they are not technically inclined to configure recipes on their own.
We are considering the following embedding options:
Recipe widget: This would expose the recipe interface, allowing users to configure action parameters directly. Is our understanding correct that users would gain access to the full recipe and its actions here?
Dynamic field mapping widget: This would allow us to send additional required parameters in the webhook payload, and then use the widget to map values into the action parameters.
Our ask:
Which widget is more suitable for our use case, where we want users to configure action parameters without overwhelming them with full recipe configuration?
What are the best practices you recommend for this type of embedding scenario?
Based on your experience, which embedding approach should we follow to balance ease of use for end-users and flexibility in configuring action parameters?
You can also suggest if there is a different widget or embedding option (other than the two mentioned above) that might better fit our use case.
