Documentation Read Markdown By OOMOL Updated 2026-10-07

Start Using Dingdang in Slack

After connecting Dingdang to Slack, use this guide to check the workspace, send a first message, and connect business data. You can also explore what Dingdang does in Slack and the PostHog demo first.

Before you start

You need a Slack workspace, a Dingdang bot with an active subscription or trial, and access to the bot’s settings. Your workspace’s app installation policy may require approval. Business tasks also need the corresponding accounts and supported App actions.

Check the bot’s workspace

Open Dingdang Console and select the intended team and bot.
Open Slack Bot under the bot’s platform connections. In the Chinese console, the entry is Slack 机器人.
Confirm the connection screen shows the connected bot and the intended workspace. In the Chinese console, the status heading is Slack 机器人已连接. If it is not connected, complete the Console workspace authorization flow first; approval follows the workspace’s installation policy.
Check that the bot is active. A saved Slack connection can remain present while the bot is paused because its subscription needs renewal.

Do not disconnect an existing workspace simply to troubleshoot a missing business-data result. First check the bot status, conversation, and business connection separately.

Send a message

Where	What to do
Direct message	Open Dingdang from Apps in Slack and send your request.
Channel	Add Dingdang to the intended channel, then mention @Dingdang in your message.

First send a DM such as “Hello, introduce yourself in one sentence.” Once it replies, try a business-data query. If DMs work but a channel does not, check that Dingdang has been added to the channel and the message @mentions it. Business-data access needs separate authorization.

Connect the source for your first task

In Connections, authorize the account that owns the information. Check the App’s supported actions and the source account’s access. If the team shares connections, verify that the intended member or group can use the connection.

For example, to find how often a product action occurred each day, ask Dingdang to read the PostHog event and chart it. The name agent_command_called below is from the demo; replace it with your own event:

@Dingdang Count agent_command_called events by day in the connected PostHog project for this month. Return the daily counts and a bar chart. State the project, period, and time zone, and mark incomplete days.

Replace the event and period with your actual question. This is an example request, not a preconfigured report.

Check the result

Confirm the project and event definition, compare at least one day’s count with the source, and distinguish event occurrences from unique users. A partial day should not be compared with a completed day as though they were equivalent.

For tasks that write a report to another App, also confirm the target account, page, and write permission. Ask for a draft before requesting the write when you need to review the content.

If Dingdang does not reply or cannot get the data

Symptom	Check first
No reply in Slack	The bot’s active status, the connected workspace, and whether Dingdang is present in the channel. Try a DM from Apps.
Console shows a paused bot or renewal notice	Restore the bot’s subscription before treating the problem as a missing Slack connection.
Replies work but business records are missing	The source App connection, source account permissions, supported action, and member/group access.
The result is plausible but differs from the source	The date range, time zone, project, filters, and metric definition.

If the issue persists, contact support with the platform, task time, observed error, and a non-sensitive description of the source. Do not include passwords, tokens, or private records unrelated to the issue.

Connection-state labels and the DM/channel instructions follow the shared Console version checked for Leina on October 7, 2026. Installation approval follows your workspace’s actual policy and connection flow.