richy.mulcahy

are you looking for a workspace wide view of tasks consumed by recipe or a more detailed history of a task consumption for a specific recipe?

So this is a bit of a hybrid answer. this exists fully for our credit based plans. This should be on the jobs themselves and then also displayed on the job history and in the Ops Hub. For the previous task based plans you should still be able to see the task consumption on the job itself and then also in the Ops Hub. The main gap is on the job history page you wont see the tasks for each job.

narasakuru are you looking specifically at MCP Apps? I think half the effort is figuring out the correct use case. Most Agentic platforms have some sort of artifact/dashboard/pages/canvas capability to visual information. MCP Apps is great if you want the end user to be able to have more live interaction. So to update a opportunity or change the stage of a ticket/issue etc. you can also have the ability to update different portions of the data using buttons etc. The catch there is understanding how your end users want to interact with the data. That Product management muscle is harder than building a dashboard.

I dont believe we have the abulity to select that in workato. you can mask data in recipes if you dont want it sent or setup a job in S3 to clear events from projects you dont care about.

have you looked at setting up audit log streaming into dynatrace? docs.workato.com/en/features/activity-audit-log-streaming

jack.zhu is there a reason you wouldnt just build this into the recipe itself? you could have a HTTP call out to a webhook recipe. this would also allow you to pass recipe data to the monitoring recipe or other logic. i would normally consider this to be a more recipe orchestration type activity

edward.williams in the past we have had people at Epicors conference. i pinged the team to see if they will be at the upcoming one. even if they arent Epicor is a longtime partner and their team is very knowledgeable about Workato. The Epicor and Workato use case question can be difficult to wrap your arms around because both products can do so much. We commonly see Epicor to CRMs for managing quotes and orders, to Ecommerce or inventory platforms, to datawarehouse and also to HR systems.

jyoti.bansal curious on why the HTTP connector was used for the sandbox? did it give more control over the dynamic queires? or different Auth supported? I love all the learnings especially the first with testing the individual actions first then building he full skill and testing it with an agent providing input. makes the troubleshooting so much easier

I recently had a customer who due to a merger had to move from Netsuite to Microsoft Dynamics Finance and Operations. It took planning by the customer to first identify how the processes will work in Dynamics and then the endpoints to be used. We looked at the connector to find gaps then determine whether connector changes or using the graph API directly makes the most sense. In General with Microsoft products navigating the Graph API is a bit trickier than with many other systems.

Since this is a Workato Owned Community connector which you can see here. if there is a bug you can submit a support ticket for our team to look at