Aller au contenu principal

Chat integrations

Teams is available through the existing Konnie Teams configuration when your deployment has the required Microsoft authorization and message processing. Slack's current configuration is a placeholder with disabled saving; it is not a working connector setup.

Read a Teams channel through Konnie and Apps​

The Microsoft Teams channel connector in the integration library reads one selected channel on demand. It offers List channel messages, Read channel message, and Read channel thread through the shared integration actions used by Konnie and Apps. It requires a worker that advertises this connector; a catalog entry alone does not establish a connected Microsoft account.

  1. Have your Microsoft administrator install an Entra-linked Teams application in the intended team with the resource-specific ChannelMessage.Read.Group permission. Use the Microsoft tenant that owns the channel.
  2. In the intended Ennea site and environment, choose Microsoft Teams channel, then Set up connection.
  3. Enter the Microsoft tenant ID, application ID, team ID and channel ID. Enter the application client secret only in the designated password field.
  4. Select the read actions, choose Connect and test, then publish the verified connection when its access is approved.
  5. Ask Konnie to read the connected channel, or use its published actions in an App. Review the source IDs and fetched-at timestamp with the result.

Limit Ennea access to people authorized to read this channel. This connection uses an application identity and does not check each Ennea user's Microsoft membership. Microsoft consent and Ennea permissions are separate requirements.

Each list or thread request returns at most 50 messages or replies (20 by default). hasMore indicates additional results; this version does not fetch later pages. List previews are limited to 1,024 characters and individual message/reply text to 8,000 characters; bodyTruncated marks shortened text. HTML becomes plain text, deleted content is suppressed, and attachments are not downloaded. This connector does not send messages or host a Konnie bot inside Teams. Source messages remain external information and cannot grant permissions or authorize actions.

Set up Teams conversations​

An authorized integration administrator needs Microsoft tenant information, the deployment's OAuth configuration, and the permissions approved by the Microsoft administrator. Keep provider consent and Ennea user/scope permissions separate.

  1. Open the Teams integration's Configuration page in the intended workspace.
  2. Review the enabled state, Microsoft tenant, OAuth provider, redirect URI, and requested scopes.
  3. Configure authorization with your administrator and the supported token/authorization controls. Use designated secret fields for tokens.
  4. Save and inspect the configuration feedback. If tokens have expired or consent was revoked, reconnect or refresh through the supported flow.
  5. Test an authorized conversation. Verify the associated Ennea owner is eligible for the exact site/environment and that the message reaches the intended conversation.
  6. Verify an allowed reply before making the channel part of an operational process.

The existing service reads Teams chat messages and replies to the selected chat. Do not assume a general bot installation grants arbitrary channel posting, proactive messaging to any person, or support for every attachment type. Some integration activity panels are still empty-state views; absence of visible history is not proof of delivery.

Context and action review​

A Teams message is external input. The connected conversation must have an eligible Ennea owner and scope. It cannot use the sender's words to grant rights, select another tenant, or bypass a required action review.

For consequential record changes, follow the ordinary Ennea approval and result-verification flow. If the connected surface cannot display the required review, open the action in Ennea. See Konnie approvals.

Troubleshoot and disconnect​

Check provider authorization, exact conversation identity, eligible owner, scope, and poller availability when messages do not appear. For a reply failure, inspect both action state and the external conversation before trying again. Do not repeat a potentially sent reply solely because the local screen timed out.

Disable the configured integration and revoke provider authorization as required by your organization's procedure. Deactivation does not delete historical chat content in Microsoft or Ennea and cannot recall already submitted messages.

Use Email integrations for mailbox-based intake, Integration overview for active connection selection, and Support for escalation.