Where it is
Connectors in the sidebar (/connectors/). The page is per study.
How it fits together
- Install the app into your Slack workspace or Discord server. This is once per workspace, not once per study.
- Mint a link code for the study and the platform.
- Redeem the code in the target channel with
/deutero connect. This binds that channel to that study. - Configure a recruitment schedule for the binding.
- Watch the Monitoring table for posts, starts and completions.
Installation credentials stay on the connector service and are never exposed to your browser.
Installing
Add to Slack or Add to Discord under Installations. Discord asks for bot and application-command scopes. Installed workspaces and servers are listed with their status.
Connecting a channel
Connect Slack channel / Connect Discord channel mints a link code, which appears in the Connected channels table. In the channel you want, run:
/deutero connect <link code>
The binding's status becomes active. Each row can be paused, resumed, or disconnected — disconnecting also stops its recruitment workflow.
Recruitment schedules
Each connected channel gets a schedule card:
| Setting | Meaning |
|---|---|
| Enabled | Whether scheduled posting runs at all |
| Interval (hours) | How often to post |
| Maximum posts | Stop after this many; blank means no limit |
| Active from / until | Only post inside this daily window |
| Active days | Which weekdays are allowed |
| Timezone | Which clock the window follows; defaults to your browser's |
| Recruitment message | What gets posted (up to 4000 characters) |
| Stop on quota | Stop posting once the study's response quota is full |
Be conservative: an interval of a few hours during working days is usually plenty. Channel members will notice a bot that posts every hour.
Monitoring
Per channel: posts made, interviews started, interviews completed, and the time of the last post.
Known issues (September 2026)
- Add to Slack is broken. It redirects to
app.deutero.ai/slack/install, which returns 404. - Minting a link code fails. Both Connect Slack channel and Connect Discord channel return "Connector API request failed" from the connector service, so no code is produced.
Discord's install redirect reaches Discord's OAuth page normally. Until the two issues above are fixed, use share links — posting your study's short URL into a channel by hand works fine, it just does not give you scheduling or per-channel monitoring.
With MCP
No connector tools. This is dashboard-only.
Privacy
Interviews run in a private conversation with the bot, not in the channel. The channel only sees the recruitment message. Members' answers are visible to you in the dashboard like any other interview, so say so in your welcome and consent text — people in a work Slack may assume otherwise.
Last updated: September 2026