Hi @mtaftferguson ,
I haven't personally tried to use outgoing webhooks with MS Teams, so someone else may have actually done this and have better advice.
It's a bit hacky, but instead of giving MS Teams the webhook url from automations, you could point it to a Data Streaming workspace url, then have a really basic workspace that creates a JSON response (like in the SO thread) and streams it back to Teams.
You'd also probably need a job submitter transformer or a HTTPCaller to actually pass on the incoming message from Teams to where you wanted it to go next.
Hi @mtaftferguson ,
I haven't personally tried to use outgoing webhooks with MS Teams, so someone else may have actually done this and have better advice.
It's a bit hacky, but instead of giving MS Teams the webhook url from automations, you could point it to a Data Streaming workspace url, then have a really basic workspace that creates a JSON response (like in the SO thread) and streams it back to Teams.
You'd also probably need a job submitter transformer or a HTTPCaller to actually pass on the incoming message from Teams to where you wanted it to go next.
That's an interesting idea that I'll definitely look into, thank you! That could be nice regardless; it'd spare us having to change configuration on the Teams side every time we had a new workspace/automation we wanted to use this pattern for.
The automation that prompted this question a beast, so I'd be looking to trigger it, rather than a single workspace/job... there's no automation equivalent of an FMEServerJobSubmitter right now, correct? I suppose that's where an HTTPCaller + webhook trigger would come in.
Edit to add: In initial testing, the data streaming workspace never gets triggered either, so Teams is either interfering sooner than that or it's user error :)
