Bots, webhooks and automations, even in encrypted conversations.

Plazer connects to the tools your community already uses. A bot answers commands, a webhook drops in notifications from other services, and a rule set up without code welcomes newcomers and hands out roles. All of it works where the conversation is end-to-end encrypted too.

Get Plazer See automations

#generalEnd-to-end encrypted

Webhook
A new release is ready to download
The changelog and checksums are on the releases page.
Bot
/poll
Saturday or Sunday? Vote with a reaction
Saturday
Sunday
Automation
Someone new joined the server, say hi. Role Newcomers assigned.

/

Type "/" and you instantly see what a bot can do.

A command is a shortcut to a bot feature. After the slash you get a list of commands with descriptions, and once you pick one, the app tells you what to type in each field, so you never have to remember the syntax.

Hints for every field: A bot describes its commands and their arguments: a date, a channel, a person or plain text. Plazer shows those hints while you type, field by field.
Only the permissions you grant: A bot gets a role like any server member. It sees only those channels and does only what its permissions allow, and you can change them at any time in server settings.
On servers and in direct messages: Use commands in channels, in threads and in a direct chat with the bot, including end-to-end encrypted channels.

/pollquestion, answers, duration
/remindwhen, text
/welcomechannel, message
/tickettopic

/

A bot in an encrypted channel is a participant, not a hole in the encryption.

In an end-to-end encrypted channel the server does not know the content. For a bot to read it, the bot has to be in the conversation just like people: with its own keys and on the list of those who hold them.

Who holds keys

You
Bot

ServerSees ciphertext only

Encrypted channel

The bot gets keys like any participant
You add the bot to the channel and from that moment it has keys to new messages, just like someone who has just joined. It cannot read the earlier history.
You see it on the list
Every integration that reads or writes in an encrypted channel is on the list of people with keys. Nobody listens in quietly through the server backend.
Remove the bot and the keys change
Once the bot is removed, the remaining participants agree on new keys. The bot cannot read anything you write afterwards.

What else is encrypted and what the server cannot see

A webhook is an address other services send messages to.

A shop, a code repository or a monitoring tool sends a short message to the webhook address, and Plazer posts it in the channel you chose. You do not write a bot or run a server: you copy the address and paste it into the service settings.

Your service

Webhook addressPOST

Server channel

The popular embed format: Plazer webhooks accept the same message and embed format that most ready-made integrations use. You move an existing integration over by changing nothing but the address.
To a channel or a direct message: A notification lands in a server channel, encrypted ones included, or straight in your direct messages.
An address you control: You create and delete webhook addresses in channel settings. Anyone who does not know the address cannot send anything through it.

What an embed is made of

AuthorReleases webhook

TitleA new release is ready to download

DescriptionThe changelog and checksums are on the releases page.

FieldsChannelstablePlatformsWindows, macOS, Linux

FooterSent by a webhook

Accent bar

The same message as JSON

1{
2  "embeds": [{
3    "author": { "name": "Releases webhook" },
4    "title": "A new release is ready to download",
5    "description": "The changelog and checksums are on the releases page.",
6    "color": 40192,
7    "fields": [
8      { "name": "Channel", "value": "stable", "inline": true },
9      { "name": "Platforms", "value": "Windows, macOS, Linux", "inline": true }
10    ],
11    "footer": { "text": "Sent by a webhook" }
12  }]
13}

No-code automations: when something happens, Plazer does the rest.

Most of what servers add bots for are simple rules. In Plazer you build them from ready-made blocks: pick an event, then pick what should happen. No code to write and nothing to host.

A newcomer knows where they are from the first minute, and the rest of the server sees who to greet.

When

Someone joins the server

Do

Post a welcome in the welcome channel
Assign the Newcomers role

Server automations in Plazer: the list of rules and the welcome rule editor that sends a message and assigns a role

Rules have their own place in the server settings

Automations are a separate tab in the server settings, next to roles, channels and moderation. Each rule turns on and off with one switch, and the preview beside the editor shows what a new person will see.

When blocks are not enough: your own bot and the API

Server economy and levels with a full admin panel.

Members earn points and server currency for being active, climb levels and unlock roles. The admin sets every rule in one panel, with no separate bot and no separate bot website.

Admin panel

Server currency: Your own name and icon for the currency members earn and spend on the server.
What earns points: Choose which activities count towards levels, and in which channels.
Level curve: Decide how much it takes to reach the next level, so you know how fast people climb.
Rewards at thresholds: Roles and channel access tied to specific levels.

Server leaderboard

Veterans
Regulars
Regulars
Newcomers

Embeds and forms for everyone, not just bots.

A rich message with a title, fields and a colour no longer needs a bot. In Plazer any server member builds one in the editor, and sends a form with questions as easily as a normal message.

New form

Tournament sign-ups

1Team name
2How many players in the line-up
3Available dates

Send to channel

Form

Tournament sign-ups

answers collected in one place

Fill in the form

Embed editor

Title, description, fields, image, accent bar and footer, with a live preview before you send anything.

Forms with questions

Sign-ups, moderator recruitment or a survey with open answers. You collect the answers in one place instead of scrolling through the channel.

Connected accounts and bridges to other messengers.

Connected accounts

Link GitHub, Steam, Spotify and other accounts to your profile. Others see straight away where to find you, and you do not have to paste links into your bio.

What a Plazer profile looks like

Bridges to other messengers

A bridge connects a Plazer channel with a conversation in another messenger. Messages go both ways, so a community does not have to move in a single day, and those still on the other side stay in the conversation.

A bot API for those who want to build more.

When the ready-made automations are not enough, you write your own bot, with a bot token, API requests, the event gateway, commands and webhooks. We will publish Plazer's code, so you will be able to check every server response at its source.

Sending a message through a webhook

1# copy the webhook address from channel settings
2$ curl -X POST "$WEBHOOK_URL" \
3    -H "Content-Type: application/json" \
4    -d @message.json

Questions about bots and integrations

What server admins ask before they move their integrations over to Plazer.

No. The bot is a participant in the conversation with its own keys, and you see it on the list of those who hold them. The server still does not know the content, and the keys change once the bot is removed.

Plazer webhooks accept the popular message and embed format, so you move most ready-made integrations over by changing only the webhook address.

No. Welcomes, reaction roles, tickets and levels are set up from ready-made blocks in server settings. You only write your own bot when you need something unusual.

Yes. You chat with a bot privately and use its commands there, including in end-to-end encrypted conversations.

Yes. You build embeds and forms in the message editor, without a bot or a webhook.

Yes. A bot gets a token, sends API requests, receives events through the gateway and registers its own commands, and messages from outside services come in through a webhook.