Note: a user with Configuration manager privileges can create and manage bots.
Bots are configured in the Bots section.
To create a bot, click Add bot.
Configure the bot:
Click Add. Pyrus will generate the parameters of a new bot and display them in a popup window:
After the bot is added, it will be available in the Bots tab. To change the configuration of your new bot, visit its profile by clicking the field with its name.
You can also disable the bot in the Status line.
You can change the security key value in the Security Key line by clicking Reset. This is useful if you suspect that the current security key is compromised. After you reset the key, the attacker will not be able to get a new token using the old key. At the same time, any previously configured bots will continue to operate.
You can set Additional rights to the bot. Use Supervisor and Configuration manager privileges.
If you want to block the bot, click Block. When a bot is deleted, it is removed from the list and the corresponding non-activated user is terminated (shown on the Terminated list in Members).
If a blocked bot user is restored, all the bot settings are restored to their previous states. You can block and restore the bot as many times as you want.
A bot configuration consists of: a URL address for calls, Security Key, ClientId, and Enabled/Disabled parameters.
URL: The address of a page on your website. The page must contain the event handler code. When a bot receives a task, Pyrus sends a request to this address. Only HTTPS addresses are allowed.
Certificate Requirements: The HTTPS certificate must be verifiable. The certificate chain must be traceable to a trusted certification center.
Security Key and ClientId values are used for API calls, and they are generated automatically when the bot is created. Security Key is used to sign each call, guaranteeing that the calls are made on Pyrus’s behalf.
{ "task_id":5600, "task":{/* task with notes */}, "access_token":"{token}" }
If required, the response body can also be specified. The response body has the same structure as the Pyrus API CreateComment request. A header authorization is not required.