> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels

> Send Human Input requests to your team's IM as cards or link messages: connect your IM, sync members, and replace or remove it

Connect your team's IM (instant messaging app) in **Settings** > **Channels**, and [Human Input](https://docs.dify.ai/en/self-host/use-dify/nodes/human-input.md) requests reach workspace members in the IM as well as by email. A workspace connects one IM.

> [!NOTE]
>
> Only workspace owners and admins see **Channels**, and only they can connect or change the IM.

How members respond depends on the IM. Some IMs show each request as an interactive card, the form itself inside the chat, and members respond right in it. Others send a message with a link, and members click the link and respond in Dify.

![Request as an IM Card](https://mintcdn.com/dify-6c0370d8/Q8QYd_xcsh-LWaCu/images/use-dify/workflow/human-input-im-card.png?fit=max\&auto=format\&n=Q8QYd_xcsh-LWaCu\&q=85\&s=d906006fd4461432ae18f85550ae59dd)

Request as an IM Card

![Request as a Link Message](https://mintcdn.com/dify-6c0370d8/Q8QYd_xcsh-LWaCu/images/use-dify/workflow/human-input-im-link.png?fit=max\&auto=format\&n=Q8QYd_xcsh-LWaCu\&q=85\&s=ac6b307c0ce4deda3ac834fd87f89e43)

Request as a Link Message

> [!NOTE]
>
> Even in an IM with cards, some forms can't be shown as one and arrive as a link message instead. See your IM's guide under [Connect Your IM](#connect-your-im) for details.

> [!NOTE]
>
> To send requests through your IM, set:
>
> * [`CONSOLE_WEB_URL`](https://docs.dify.ai/en/self-host/deploy/configuration/environments#console_web_url) and [`APP_WEB_URL`](https://docs.dify.ai/en/self-host/deploy/configuration/environments#app_web_url) = addresses recipients can open
> * For an IM that [shows requests as cards](#connect-your-im), [`TRIGGER_URL`](https://docs.dify.ai/en/self-host/deploy/configuration/environments#trigger_url) = an address your IM can reach over the internet, so clicks on card buttons get back to Dify
>
> Email requests also need the deployment's [mail configuration](https://docs.dify.ai/en/self-host/deploy/configuration/environments.md#mail-configuration).

## Connect Your IM

In your IM, create a custom app for Dify that can send messages as a bot and read the member directory so Dify can match members by email. Then enter the app's credentials in **Channels**. In an IM that shows cards, also set the app to send button clicks back to Dify.

Follow the guide for your IM:

| IM | Requests arrive as |
| :- | :- |
| [Slack](https://docs.dify.ai/en/self-host/use-dify/workspace/channels/slack.md) | Card |
| [Feishu / Lark](https://docs.dify.ai/en/self-host/use-dify/workspace/channels/feishu-lark.md) | Card |
| [Microsoft Teams](https://docs.dify.ai/en/self-host/use-dify/workspace/channels/ms-teams.md) | Card |
| [DingTalk](https://docs.dify.ai/en/self-host/use-dify/workspace/channels/dingtalk.md) | Link message |
| [WeCom](https://docs.dify.ai/en/self-host/use-dify/workspace/channels/wecom.md) | Link message |

If another IM is already connected, check [what replacing clears](#replace-or-remove-your-im) first.

## Sync Members

After connecting, click **Sync now** to bind members' IM identities. Dify reads your IM's member directory (as far as your IM app is allowed to see it) and binds each IM identity to the workspace member with the same email.

Only members with a bound IM identity get requests in the IM. You can [bind anyone the sync misses by hand](https://docs.dify.ai/en/self-host/use-dify/workspace/contacts.md#bind-by-hand).

A sync runs only when you click **Sync now**, so sync again after people join your workspace or your IM, or after someone's email changes.

When a sync finishes, click **View details** to see what it changed:

* **Added**: IM identities newly bound to a member.
* **Not matched**: IM identities the sync couldn't pair with a member. Everyone on your IM who isn't in the workspace lands here. For a member who should have matched, see [Contacts](https://docs.dify.ai/en/self-host/use-dify/workspace/contacts.md#sync-with-your-im) for the causes and fixes.
* **Failed**: the whole sync failed, and nothing changed. Check your IM app's credentials and its permission to read the directory, then sync again.
* **Removed**: bindings the sync deleted because the IM identity is no longer in the directory, such as a deactivated account or one your IM app can no longer see. Under each IM identity:
  * "No longer in the directory": no other IM identity took its place, so the member is now unbound and gets requests by email only. If they're still on your IM, make sure your IM app can see them, sync again, and [bind them by hand](https://docs.dify.ai/en/self-host/use-dify/workspace/contacts.md#bind-by-hand) if the sync doesn't match them.
  * "Binding replaced": a new IM identity with the member's email took its place, and the member also appears under **Added**.
* **Skipped**: IM identities already bound, by an earlier sync or by hand. The sync keeps those bindings.

## Replace or Remove Your IM

To switch to another IM, click **Replace** on it in **Channels**. To stop using IM, delete it.

> [!WARNING]
>
> Replacing or deleting the IM:
>
> * Clears every IM binding, including the ones made by hand, along with the sync history.
> * Breaks the cards already sent: their buttons stop working, and the cards don't update when someone responds elsewhere. Emails and link messages already sent keep working, so people can still answer waiting requests from there.

Updating credentials for the same organization, such as after resetting the App Secret, keeps the connection and its bindings. Saving credentials from another organization in the same IM, such as moving from a Feishu test organization to your company's, replaces the connection.

After replacing, sync and redo any bindings you made by hand. For an IM that shows cards, also set the new Callback URL in its app.

After deleting, Human Input nodes keep their recipients and settings, and new requests go out by email only.

## Troubleshooting

> [accordion] A request never arrived in the IM
>
> Check that:
>
> * The person's contact shows your IM as bound. If it doesn't, sync again or [bind them by hand](https://docs.dify.ai/en/self-host/use-dify/workspace/contacts.md#bind-by-hand).
> * Your IM is still connected in **Channels**.
> * Your IM app's credentials still work. **Channels** keeps showing the IM as connected after they stop working, so open the IM's settings in **Channels** and click **Test connection** to find out.
> * Your IM app has the permissions to send, and is published or installed for that person.
>
> Meanwhile, the person still has the request by email if the deployment's [mail configuration](https://docs.dify.ai/en/self-host/deploy/configuration/environments.md#mail-configuration) is set up.

> [accordion] A button on a card doesn't work
>
> * The request is already closed: someone responded, it timed out, or the run was stopped. Start a new run if the decision is still needed.
> * The Callback URL in your IM app is missing, out of date, or unreachable. Copy the current one from **Channels** into the app. It changes whenever [`TRIGGER_URL`](https://docs.dify.ai/en/self-host/deploy/configuration/environments#trigger_url) changes. If it's already current, check that `TRIGGER_URL` is set to an address your IM can reach over the internet.
> * The card was sent before you replaced the IM or rebound the person's IM identity. Those cards stay broken, but the person can still respond from their email if the deployment's [mail configuration](https://docs.dify.ai/en/self-host/deploy/configuration/environments.md#mail-configuration) is set up.

For causes specific to your IM, see the troubleshooting in its guide under [Connect Your IM](#connect-your-im).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.