As I understand, all notifications will be fired using one discourse user. For me that’s a bit rigid. Ideally I need different users for different channels. Our discourse will serve company wide purposes, andalso support projects, which are kind of private.
But, as a workaround / simple solution I can live with a setup, where there are implicit rules like: mute all categories, which are not public. That way if I create a new category for a new project, posts from that new category won’t appear in the company wide channel.
Yes, the issue was related to the SSL certificate. It has been solved. Thanks for the immediate help
Another big thing is, I am embedding the discourse subdomain into our react product. Whenever a user clicks on slack notification of topic/post creation , our intended goal is to redirect user to our product’s domain, instead of discourse subdomain. I am not able to set this redirection. Kindly suggest any way.
I created the slack app as per the instructions. The issue I’m having is that other users want to add notifications to private channels I don’t have access to.
Is there a way to notify private slack channels that the creator of the slack app doesn’t have access too?
Or how can other users grant permissions to the app?
Also if I understand correctly, those slack app tokens that are entered into the Discourse’s plugin configuration allow access to my private channels, correct? This might be undesirable since any Discourse admin can see those tokens in the settings section. Would be good to warn about that, or remove from the instructions the groups:history and im:history grants.
Our makerforums discourse is intended to bring together a lot of related but separate communities. These communities are organized in our discourse by category or sub-category. Some of these communities have their own slack spaces.
At least one community, associated with a sub-category, would like slack integration, but as far as I can tell, there can be only one for the whole discourse.
Unfortunately you can only have one slack community connected at the moment. It would be nice to allow multiple connections per-provider in the future.
Thanks for confirming. It looks like it would be substantial work to move to installing arbitrarily many chat integrations, especially to do so without backward compatibility problems.
For anyone else with this problem: As an alternative we are exploring for one-way notification in slack that posts have been made in discourse, we realized that it makes sense to take advantage of Discourse’s RSS support and hook up the slack RSS app:
For the next person who sees this: I saw 422 No Record in the slack integration when trying to send a test message from the admin interface in my discourse.
The logs (https://mydiscourse/logs) showed the real error, which was in my case "{\"ok\":false,\"error\":\"channel_not_found\"}"}
The reason was that /discourse watch in a private channel of the Staff category showed up with a slack channel name like #private instead of the actual channel name, so I had to set the correct channel name in the discourse administrative interface to the actual channel name; then it worked.
Hola @david, ¿hay alguna manera de configurar una integración unidireccional (de Discourse a Slack) usando el plugin discourse-chat-integration?
Me gustaría configurar un webhook de Slack al que se envíen los mensajes, sin necesidad de configurar una nueva aplicación en Slack.
Seguí las instrucciones de Discourse to Slack (one-way) integration, pero no lo logré. Después de habilitar el plugin y configurar la URL del webhook, no encontré ningún panel de control para continuar con la configuración.
Necesitas habilitar el complemento, agregar la URL del webhook y habilitar el proveedor “slack”. La configuración se llama “chat integration slack enabled”. Una vez que hayas hecho eso, deberías ver la pestaña de Slack en tu panel de administración (en complementos → integraciones de chat).
He seguido esta guía para configurar nuestra integración de Discourse con Slack.
Al probar la regla, obtengo este error DiscourseChat::ProviderError, pero sin ningún detalle; incluso la consola del navegador no proporciona mucha información sobre el error.
¿Tienes alguna idea sobre la causa?
Desafortunadamente, Slack no nos proporciona el nombre del canal especificado por el usuario en la API de comandos de barra, así que tenemos que usar el ID (más detalles en el mensaje del commit). Si siempre usan comandos de barra para gestionar las reglas, no habrá ninguna diferencia.
He estado intentando que el bot de Slack funcione con un canal durante demasiado tiempo. ¿Hay algún truco que me esté faltando para permitir que Discourse publique en un canal público? Puedo recibir notificaciones directamente desde Discourse, pero parece que Discourse no puede publicar en un canal. Iba a agregar el webhook entrante a la integración, pero la descripción emergente de Discourse indica que no es recomendable. Cualquier ayuda sería muy apreciada.
Ok, encontré un post en otro foro que me mostró un lugar diferente donde estaban los registros. El error fue bastante claro: el usuario del bot tenía que ser agregado al canal público para publicar en él. No esperaba que fuera necesario, ¡pero esa es la solución!
