Hi Folks, Still playing to find a workaround for scheduling assistant job every morning ... without success. Context : @MeetingDailyCheck is called on a daily basis in order to check my today meeting on my Google calendar. Workflow :
Working perfectly through the UI (cf. screenshot named workflow1.png)
Working perfectly though Slack, by typing the command @dust +MeetingDailyCheck(cf. screenshot named workflow2.png)
Not working when launching the same command in slack through API via Make (cf. screenshot named workflow3.png)
Neither working while testing with custom API call and using "skipToolsValidation" directive
Error message : On workflow 3, calling Google calendar tools service is falling with The tool google_calendar__list_events returned an error. An error occurred while executing the tool. You can inform the user of this issue. Any insight Dust team please ? Is there some hard limitation for now or for ever ? Thank in advance
Hey Baudouin MARBACH, it’s because skipToolValidation only work if the MCP is a “Workspace Credential” versus a “Personal Credential” Because via API call he cannot know who trigger the API call (as the token is a global token for your Dust’s workspace) cc Stephen (Dust)
Thanks Greyg Sinigaglia de Malibran for this is insight. I'm currently using the native Google calendar integration, configured for the all Dust workspace (cf. screen). I'm currently the only user and admin in my Dust organization. So I guess I've set it up correctly. Is that correct ?
Baudouin MARBACH The key setting is here: under Credentials you can see that for our company I have set it up as personal credentials. This way every employee logs in with their own account instead of every employee seeing calendar data from one authenticated account, e.g. mine. As per Greyg Sinigaglia de Malibran, calling an agent like this through API fails because it doesn't know which Google Calendar token it should use since the API access is general for the whole Company Space, not per user. I suppose this is something for the DUST team to solve. Either incorporate time-based triggers inside of DUST, or expose API endpoints on the per-user level.
Baudouin MARBACH the workaround, until DUST team implements this, is to pull the calendar data yourself as the 1st step inside of make.com/zapier. Then use an agent without access to a specific calendar tool and instead feed it the data you pulled in the previous step - ofc, in such a set-up, DUST as such is redundant, since you can set-up your agent inside of make/zapier. But you can also use DUST agent if that's easier.
Yep that would be the workaround. Thanks Tomas. The fact is this assistant is calling another one with tools as well. Will try anyway.
