Back to Work

Discord automation / Collaboration workflows

InkBot

Role
Designer / Developer
Discipline
Discord automation / Collaboration workflows

Project imagery

Discord conversation showing an InkBot group request command and the resulting request flow.

Focus

  • Discord automation
  • Collaboration workflows
  • Role targeting
  • Interaction states

Core feature

  • Group Request / SOS recruitment flow

01 / Collaboration workflow

How could people recruit collaborators inside Discord?

InkBot started as a tool to help me manage the InkVein Discord server more effectively. I had a few moderation and community commands in mind, but the main feature I wanted was a better way for people to find and recruit collaborators directly inside Discord.

The core command was a Group Request. A user could specify how many collaborators they needed, which Discord role they were looking for, and a short description of the work:

!group 3 developer Looking for help building a portfolio bot demo.

Group Request workflow

InkBot group request announcement showing the requested role, target count, channel, and original poster.
Group request announcement
InkBot group request help response showing command syntax, targets, and an example.
Group request help
InkBot roles command showing available creative and development roles.
Roles command

02 / Participation state

What would I improve next?

InkBot would turn that into a structured request inside Discord. It made the ask visible to the right role, showed who created it, and gave members a clear way to respond. Members could join by reacting with 🤝 or contacting the request owner directly.

If the request did not reach its target number of collaborators within a specified time, InkBot could send an SOS style follow up to the relevant roles. That gave the request another chance to reach people before its TTL expired.

If I continued the project today, one of the first improvements I would make would be clearer participation state. For example, when someone joins a request, InkBot could post “@Player joined the request” so the group owner could quickly see who has committed without manually checking reactions.

That made the project less about commands alone and more about making collaboration state visible inside a community.