Currently it's not possible to serve multiple channels of the same type, e.g. it is not possible to provide two Slack credentials and thereby supply to Slack channels.
Ideally something like this should be possible:
slack:
slack_token: "1234"
slack_channel: "@my_channel"
slack:
slack_token: "5678"
slack_channel: "@another_channel"
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@erohmensing You didn't do this, right?
no, not two channels at once. i think this would go into that question how the bot handles multiple users at once. as of my changes the slack channel posted to can be dynamic though, it's not restricted to that defined in credentials
so what happens with this issue? Maintenance?
@wochinge do you remember who was asking for this? the slack token isn't per channel so I don't think that would be the implementation to handle this, but i guess this is how we could handle multiple workspaces, not sure if we want to do that
well someone literally just asked for this: https://forum.rasa.com/t/setting-up-multiple-facebook-chatbots-pages/11844
I put it in maintenance. Could be a bit tricky if the same user is speaking to multiple bots. Probably some sender_id prefix would be required.
I don't think this is a very common scenario and I doubt we should implement this right now. But if someone wants to do it, I'd rather use an array:
slack:
- slack_token: "1234"
slack_channel: "@my_channel"
- slack_token: "5678"
slack_channel: "@another_channel"
My company would be very interested in this being supported. We have one Facebook app that we want to connect to multiple pages.
We then want to use the conversations/{{sender_id}}/execute API to send custom messages to specific senders. However, in the handler we do not have access to the sender_id anymore. We need this in order to obtain the page id from our storage.
Having a list of subchannels per channel would be very handy :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
My company would be very interested in this being supported. We have one Facebook app that we want to connect to multiple pages.
We then want to use the
conversations/{{sender_id}}/executeAPI to send custom messages to specific senders. However, in the handler we do not have access to thesender_idanymore. We need this in order to obtain thepage idfrom our storage.Having a list of subchannels per channel would be very handy :)