Getting started

In ten minutes: the Tsuaa bot on your server, and a /hello command it answers.

Add the bot

1. Sign in to the dashboard with your Discord account. The Your servers page lists your servers.
2. Under Add Tsuaa to a server, pick yours and click Install. You need to manage the server on Discord (Administrator or Manage Server): Discord requires it.
3. Discord shows the permissions the bot asks for, never Administrator. Keep them all if you can: a node whose permission is missing is flagged, and the server's Bot page lets you grant it later. The detail: Bot permissions.
4. Back on Tsuaa, the server shows under With Tsuaa. Open it: the home shows your first steps, ticked as you go.

A server where Tsuaa is already installed but that you don't manage shows under Ask for access: its managers open the dashboard to you, then choose what you'll be able to do there (Team and permissions).

A server without Tsuaa you're not admin of is folded at the bottom of the page: Propose Tsuaa prepares a message with the install link, to send to its admins on Discord. The link is all they need, even without a Tsuaa account.

Create a Blueprint

1. Click New Blueprint. Give it a name, such as "Hello", choose A command under Start with, then Create.
2. The editor opens with two nodes: the Command, and the Slash Command Event that fires when a member uses it. Select the Command and, in the Properties panel, give it a name (hello) and a description.
3. In the toolbar at the bottom, open Discord and drop Reply to Interaction. Write the message, such as "Hello!". To slip in the member's name or other data, see expressions.
4. Link the Event's output to the Action: drag from its port to the node. The draft saves itself.

A blocking issue shows in red in the status bar, at the bottom of the editor: a click lists the problems, each with its node. The editor tour and how data flows go further.

Test it

Test mode runs your draft on the real server, but only for testers. On the Team page, open Server owner (or Server managers) and turn on Tester for yourself: not even the owner has it by default. Then click Test in the editor. Use /hello on Discord: the execution shows live on the canvas.

Put it online

Deploy puts the draft online for the whole server. The Blueprint costs credits while it runs: 150 per server, and a command with its reply costs little (Limits and credits). From then on, editing the draft changes nothing that runs until you deploy again (Lifecycle).

What next

• Give your team rights in the Team page: view, create, edit, deploy, test (Team and permissions).
• Keep a value from one execution to the next with Variables.
• Branch a Blueprint with Conditions.
• Follow what runs in the Analytics and the log.
• A question? Getting help.