🎁 Right in time for the holidays, take the 2027 State of Integrations Survey and be entered for a chance to win a $250 visa gift card. Survey closes 12/15. 🎁

Connector CategoryChat

Security alerts don't wait for someone to check a dashboard.

Synqly connects your product to the chat and collaboration platforms your customers use through a single API, so security events surface as actionable messages inside Slack, Microsoft Teams, and AI-powered assistants, without custom webhook code for each platform.

Newest capabilities

See details
Added November 8, 2026

Create Direct Message

CategoriesChat
ProductSlack
Added November 8, 2026

Create Message

CategoriesChat
ProductSlack
Added November 8, 2026

Delete Message

CategoriesChat
ProductSlack

Bi-directional integration

Security teams work in chat, not consoles.

Security operations teams work in Slack channels and Teams workspaces, triage alerts in threads, and increasingly interact with AI assistants embedded in their collaboration tools. Products that reach people where they already work, and that can receive input back, close the loop between detection and response faster than any dedicated console.

Synqly's Chat connector gives your product normalized, bi-directional access to the collaboration platforms your customers use. Send structured messages and alerts, post updates to running threads, surface findings inside AI assistants, and receive user input back into your workflows, all through a single integration surface.

Team chatChannelsAI assistants

Your customer's Chat tools

Synqly Chat APINormalized model across providers
Your product

What your product can do with Chat integrations

Four patterns product teams build on the Chat connector.

01

Security alerts in the right channel

Route security events from your product to the correct Slack channel or Teams workspace based on severity, team ownership, or affected asset, so alerts reach the people who can act on them immediately.

02

Investigation threads

Post structured investigation updates, evidence summaries, and timeline entries directly into active collaboration threads so responders stay in sync without switching between tools.

03

AI assistant integration

Surface security findings and present response options through Microsoft 365 Copilot and other AI-powered collaboration assistants, giving analysts a natural language interface to your product's data.

04

Approval and response workflows

Receive user input, approvals, and acknowledgments from chat platforms back into your product's workflow engine so human-in-the-loop decisions can happen where teams already communicate.

Providers

All these Chat providers, one unified API

Each provider links to its integration page with setup details and supported operations.

API Reference

Chat technical capabilities

chat_add_on

Create Direct Message

Sends a direct message to one user, opening the direct conversation if it does not exist yet. The response's `chat_message.conversation_uid` addresses that conversation for later messages and reads.

add_comment

Create Message

Posts a message to a conversation as the integration's bot or app, either as a new top-level message or as a reply in a thread. The response carries the message's `uid`, which update_message and delete_message accept.

speaker_notes_off

Delete Message

Deletes a message the integration sent. Messages sent by anyone else cannot be deleted, and a provider's admin policy can forbid deletes.

groups

Query Conversation Members

Returns the members of a specific conversation. Use the user-scoped variant (query_user_conversation_members) for chats that only exist in a user\'s mailbox (e.g. Teams 1:1 chats).

forum

Query Conversation Messages

Returns messages from a specific conversation. The conversationId must be obtained from query_conversations or query_user_conversations. Use the user-scoped variant (query_user_conversation_messages) for chats that only exist in a user\'s mailbox.

chat

Query Conversations

Returns a list of conversations (channels or workspaces) not scoped to a specific user. Providers that can only enumerate conversations per-user return NotImplemented; use query_user_conversations instead.

business_messages

Query Messages

Returns all messages across every conversation in the connected workspace or tenant.

group

Query User Conversation Members

Returns the members of a conversation scoped to a specific user. Required for providers where conversations are only addressable via the user (e.g. Teams DMs, Copilot AI sessions).

mark_chat_unread

Query User Conversation Messages

Returns messages from a conversation scoped to a specific user. Required for providers where conversations are only addressable via the user (e.g. Teams DMs, Copilot AI sessions).

chat_bubble

Query User Conversations

Returns a list of conversations scoped to a specific user — DMs, group chats, or (for AI providers) synthesised sessions.

person_search

Query Users

Returns a list of users in the connected workspace or tenant. Used to discover whose conversations can be queried.

rate_review

Update Message

Replaces the text of a message the integration sent. Messages sent by anyone else cannot be updated, and a provider's admin policy can forbid edits. The response can lack `chat_message.parent_uid`; the `create_message` response for a reply carries it.

Ship Chat integrations in days, not quarters.