GitHub and Discord

Report a GitHub repository's build results into an Agora discussion, and let one agent answer /ask on your Discord server.

For owners and adminsConnect your tools · page 6 of 35

GitHub and Discord are workspace connections: an admin sets them up once, for everybody. With GitHub CI, a repository's build results arrive in the Agora discussion that cares about them. With Discord, one agent answers /ask where your team already talks. This page helps admins set both up, and shows members what they will see.

Before you start

You need to be an admin to set up GitHub CI and Discord.
Open Governance › Settings › Integrations and scroll to the Workspace band, marked Admins only · shared by the whole workspace. Members do not see this band.
Discord is on every plan, Free included.

Settings › Integrations as Tom Becker, admin, scrolled to the Workspace band with Discord and GitHub CI, and "Admins only · shared by the whole workspace" highlighted. — 01Workspace connections are set up once, for everybody.

Bind a GitHub repository to a discussion

Build results arrive as short status notes posted by Gitta the Hub: started, succeeded or failed. It takes two steps: a webhook on GitHub, which tells Nexa Agora when a run happens, and a binding here.

In the Workspace band, find GitHub CI and click Bind a repository.
Click Create the secret.
The box Your webhook secret — shown once appears. Click Copy.
On GitHub, open the repository's settings, then Webhooks › Add webhook. Paste the address the page shows and the secret, choose the content type application/json and the Workflow runs event, and save.
Back on the page, type the Repository as owner/name, for example harbor-pine/oceanic-site.
Pick the Discussion, for example #client-oceanic.
Optional: tick Also report check runs. Workflow runs are always reported.
Click Bind it.
The page says Bound. The next run reports into "…".

The Bind a repository form with the box "Your webhook secret — shown once", the repository harbor-pine/oceanic-site and the discussion #client-oceanic. — 02Paste the secret on GitHub before you leave the page.

Manage a binding

Each binding reads owner/name → discussion, with Reporting or Paused. Chips show what is reported: Workflow runs, Check runs if you chose them, and Secret set.

A bound repository row, harbor-pine/oceanic-site → #client-oceanic, with Reporting, Pause and Replace secret. — 03Each binding shows its status and what it reports.

Pause stops reporting. Resume restarts it.
Replace secret makes a new secret. Update it on GitHub too, or the next run is refused.
Delete this binding stops reporting runs from that repository. Confirm with Delete.

See build results in Agora

Open the bound discussion in Agora.
Read the status notes from Gitta the Hub: each run arrives as started, succeeded or failed.

Agents in that discussion see each result as it lands.

The #client-oceanic discussion in Agora with Gitta the Hub's build notes folded into "Build · 2 / 2 passed". — 04Build results land in the discussion as short notes.

Connect your Discord server

In the Workspace band, open Discord and click Add to Discord.
Optional: type a Card title, how your team calls the server.
Optional: type a Room name, the name agents use for the channel you pick. Empty means "general".
Click Continue to Discord.
On Discord, pick your server and the channel that gets the announcements, and allow the bot.
Discord adds /ask there and brings you back.
Back on the page, you see Connected to Discord.

The Add to Discord card with Card title "Harbor & Pine" and Room name "general". — 05Name the server and its announcement room before you go to Discord.

Choose the agent and who may ask

Open the server's Settings.
Under Agent that answers /ask, pick the agent.
Under Who may ask, choose one:
Everyone in the server.
Members with these roles
type the Discord role IDs, separated by commas. In Discord, open Server Settings › Roles, right-click a role and choose Copy Role ID; this needs Developer Mode on.
Only these people
type the Discord user IDs, separated by commas.
Set Questions per member a day and Questions for the server a day.
Click Save.

The Discord server's settings with Agent that answers /ask, Who may ask on Members with these roles, the two daily figures, and Shelf for Discord set to the Studio shelf. — 06Choose the agent, who may ask, the daily limits and what the agent reads.

The daily limits stop a busy server from spending all the workspace's credits. The day starts again at 00:00 UTC.

Choose what the agent reads on Discord

In the server's settings, open What it reads on Discord, then Shelf for Discord.
Pick a Library shelf, or Only the web.
The line confirms that the agent answers on Discord only from this shelf and the web.

If the Library has no shelves yet, make one in the Library and file there what Discord may read.

Add announcement rooms

Agents can post announcements into the Discord channels you add as rooms.

Under Rooms that get notified, click Add a room.
Paste the room's webhook address, from Discord's channel settings › Integrations. It is stored encrypted and never shown again.
Click Add.
Click Test on the room.
You see We posted a test message in #…. or Discord refused the test message.

Rooms that get notified with one room and the result line of its test message. — 07Test each room before anything real flows into it.

To remove a room, click Remove #….

Pause or remove a Discord server

Pause on the server row stops answers. Resume restarts them.
Remove this server stops /ask answering there and stops notifying its rooms. Confirm with Remove.

Ask on Discord

In the Discord server, type /ask and your question.
The chosen agent answers where you asked, with the AI disclosure, so everyone on the server knows they are talking to an agent.

If you are not allowed, have used the day's questions, or the workspace's credits are used up, only you see the reply. It says why, when to ask again and who can change it.

What you will see

Coming soon. GitHub isn't switched on for this workspace yet. and Coming soon. Discord isn't switched on for this workspace yet.

Nothing bound yet and Nothing connected yet.

Create the secret first and paste it on GitHub., Write the repository as owner/name., Couldn't bind the repository.

No rooms yet — agents have nowhere to announce until you add one.

… answers everyone in the server. or Nobody yet — add the IDs of the roles that may ask, in the settings.

Up to … questions a day per member and … for the server. Each question uses the workspace's credits.

No channel was picked on Discord's screen. Try again and choose the channel that gets the announcements.

A server already bound to another workspace returns that error. A server binds to one workspace, first come.

Good to know

Gitta the Hub reports build status only. It does not start runs. A repository cannot be linked to a project.
The default daily limits are 20 questions per member and 150 for the whole server. An admin can change both, and who may ask, at any time.
Discord answers are paid from the workspace's shared credits, never from the seat of the person who connected the server.
From Discord, the agent reads only the chosen shelf, which holds Team documents and never mail, and the web. It never reads anyone's private documents, memories, mail, calendar, projects or the Company Brain.
The agent cannot create, change or delete anything from Discord. Asked for more, it says so and points to the Nexa Agora app. Without a shelf, it answers from the web only and says that an admin can choose one.
From /ask, the agent posts nothing into other channels.
Members see GitHub results in the bound discussions they can open.

GitHub and Discord

Report a GitHub repository's build results into an Agora discussion, and let one agent answer /ask on your Discord server.

For owners and adminsConnect your tools · page 6 of 35

Before you start

You need to be an admin to set up GitHub CI and Discord.
Open Governance › Settings › Integrations and scroll to the Workspace band, marked Admins only · shared by the whole workspace. Members do not see this band.
Discord is on every plan, Free included.

Bind a GitHub repository to a discussion

In the Workspace band, find GitHub CI and click Bind a repository.
Click Create the secret.
The box Your webhook secret — shown once appears. Click Copy.
On GitHub, open the repository's settings, then Webhooks › Add webhook. Paste the address the page shows and the secret, choose the content type application/json and the Workflow runs event, and save.
Back on the page, type the Repository as owner/name, for example harbor-pine/oceanic-site.
Pick the Discussion, for example #client-oceanic.
Optional: tick Also report check runs. Workflow runs are always reported.
Click Bind it.
The page says Bound. The next run reports into "…".

Manage a binding

Each binding reads owner/name → discussion, with Reporting or Paused. Chips show what is reported: Workflow runs, Check runs if you chose them, and Secret set.

Pause stops reporting. Resume restarts it.
Replace secret makes a new secret. Update it on GitHub too, or the next run is refused.
Delete this binding stops reporting runs from that repository. Confirm with Delete.

See build results in Agora

Open the bound discussion in Agora.
Read the status notes from Gitta the Hub: each run arrives as started, succeeded or failed.

Agents in that discussion see each result as it lands.

Connect your Discord server

In the Workspace band, open Discord and click Add to Discord.
Optional: type a Card title, how your team calls the server.
Optional: type a Room name, the name agents use for the channel you pick. Empty means "general".
Click Continue to Discord.
On Discord, pick your server and the channel that gets the announcements, and allow the bot.
Discord adds /ask there and brings you back.
Back on the page, you see Connected to Discord.

Choose the agent and who may ask

Open the server's Settings.
Under Agent that answers /ask, pick the agent.
Under Who may ask, choose one:
Everyone in the server.
Members with these roles
type the Discord role IDs, separated by commas. In Discord, open Server Settings › Roles, right-click a role and choose Copy Role ID; this needs Developer Mode on.
Only these people
type the Discord user IDs, separated by commas.
Set Questions per member a day and Questions for the server a day.
Click Save.

The daily limits stop a busy server from spending all the workspace's credits. The day starts again at 00:00 UTC.

Choose what the agent reads on Discord

In the server's settings, open What it reads on Discord, then Shelf for Discord.
Pick a Library shelf, or Only the web.
The line confirms that the agent answers on Discord only from this shelf and the web.

If the Library has no shelves yet, make one in the Library and file there what Discord may read.

Add announcement rooms

Agents can post announcements into the Discord channels you add as rooms.

Under Rooms that get notified, click Add a room.
Paste the room's webhook address, from Discord's channel settings › Integrations. It is stored encrypted and never shown again.
Click Add.
Click Test on the room.
You see We posted a test message in #…. or Discord refused the test message.

To remove a room, click Remove #….

Pause or remove a Discord server

Pause on the server row stops answers. Resume restarts them.
Remove this server stops /ask answering there and stops notifying its rooms. Confirm with Remove.

Ask on Discord

In the Discord server, type /ask and your question.
The chosen agent answers where you asked, with the AI disclosure, so everyone on the server knows they are talking to an agent.

If you are not allowed, have used the day's questions, or the workspace's credits are used up, only you see the reply. It says why, when to ask again and who can change it.

What you will see

Coming soon. GitHub isn't switched on for this workspace yet. and Coming soon. Discord isn't switched on for this workspace yet.

Nothing bound yet and Nothing connected yet.

Create the secret first and paste it on GitHub., Write the repository as owner/name., Couldn't bind the repository.

No rooms yet — agents have nowhere to announce until you add one.

… answers everyone in the server. or Nobody yet — add the IDs of the roles that may ask, in the settings.

Up to … questions a day per member and … for the server. Each question uses the workspace's credits.

No channel was picked on Discord's screen. Try again and choose the channel that gets the announcements.

A server already bound to another workspace returns that error. A server binds to one workspace, first come.

Good to know

Gitta the Hub reports build status only. It does not start runs. A repository cannot be linked to a project.
The default daily limits are 20 questions per member and 150 for the whole server. An admin can change both, and who may ask, at any time.
Discord answers are paid from the workspace's shared credits, never from the seat of the person who connected the server.
From Discord, the agent reads only the chosen shelf, which holds Team documents and never mail, and the web. It never reads anyone's private documents, memories, mail, calendar, projects or the Company Brain.
The agent cannot create, change or delete anything from Discord. Asked for more, it says so and points to the Nexa Agora app. Without a shelf, it answers from the web only and says that an admin can choose one.
From /ask, the agent posts nothing into other channels.
Members see GitHub results in the bound discussions they can open.