slack integration native does not work
ART-2035_KNOWLEDGE_NODE-60
hidden.\n\n![]()\n\nSlack currently does not support custom objects or related automations.\n\nSlack snap-in user resolution\n-----------------------------\n\n* The Slack snap-in uses email for user resolution between platforms. If a user or organization hides their emails, the integration cannot resolve the user to a DevRev Contact and will act on behalf of itself instead. It's recommended to ask customers to share their emails with your organization so apps, including DevRev, can access
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-28
maintain one public connection per DevRev organization. Within an organization, one Slack connection can be used across multiple snap-ins and workflows. Creating multiple connections may disrupt existing integrations.\n* Connecting with Slack enterprise workspace is currently in limited availability. If you have a Slack Enterprise account, please contact DevRev Support to be whitelisted before attempting setup.\n\n1. Search and open [Slack](https://marketplace.devrev.ai/one-slack) in the DevRev
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-57
**Slack snap-in event discussions panel** to automatically invite the DevRev app to all public channels.\n  + Private channels still require manual addition.\n\n### When sync is not possible\n\nIf sync isn\xe2\x80\x99t possible, the form will display a clear warning. Possible reasons include:\n\n* The thread is already in sync with another DevRev object.\n* Sync is not supported for the object in the given Slack channel.\n* The DevRev app is not a member of the channel.\n* The channel is
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-56
accounts, or AI agents in DevRev aren\xe2\x80\x99t synced to Slack. To change this, enable the **Sync bot messages from DevRev to Slack** option in snap-in configurations.\n* The snap-in supports syncing of message edits and deletions between platforms.\n* Message attachment sync is supported both ways, with a file size limit of 250MB.\n\n### Inviting DevRev app to channels\n\n* Adding the DevRev app to many Slack channels can be challenging at scale.\n* Use the /SlackInviteBot command from the
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-55
Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection   - DevRev object ID   - Slack channel ID | N/A |\n\nAdditional capabilities and limitations\n---------------------------------------\n\n### 2-way sync between DevRev and Slack\n\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\n* By default, messages from bots, service
Slack | Integrate | Snap-ins | DevRev
ART-15716_KNOWLEDGE_NODE-0
b'Support QueryIntegration and API Questions\n\nAPI Support in DevRev\n\nYes, DevRev provides robust APIs for automation, integration, and custom workflows. You can use REST APIs to interact with tickets, issues, users, and more.\n\n[Learn more about DevRev APIs](https://devrev.ai/docs/api)\n\n2. Slack User Permissions Needed for Slack Integration\n\nTo integrate DevRev with Slack, you need to be a Slack workspace admin or have permission to install apps. The integration requires permission to
Support queries related playbook
ART-15716_KNOWLEDGE_NODE-1
read messages, post messages, and access user info in the selected channels.\n\n[Slack integration setup guide](https://devrev.ai/docs/integrations/slack)\n\n3. Jira Integration with Label-Based SyncYou can connect DevRev to Jira using the Jira snap-in. During setup, you can configure filters to sync only issues with a specific label by setting up the appropriate JQL (Jira Query Language) filter in the integration settings.\n\n[DevRev\xe2\x80\x93Jira integration
Support queries related playbook