2 title = "Email & Webhooks"
5 slug = "email-webhooks"
6 aliases = ["email-config"]
9 Within BookStack email is used in various ways relating to user management & authentication.
10 Outgoing webhooks are available as a mechanism to extend BookStack or notify in an event-driven manner.
12 - [Email Configuration](#email-configuration)
13 - [Outgoing Webhooks](#outgoing-webhooks)
14 - [Async Action Handling](#async-action-handling)
18 ### Email Configuration
20 BookStack sends out emails for a range of purposes such as email-address confirmation & "forgot password" flows.
21 Both SMTP and Sendmail (Linux Sendmail) are supported email mechanisms.
25 To get up and running with SMTP you will need to add, or set, the following variables in your `.env` file:
30 # Host, Port & Encryption mechanism to use
31 MAIL_HOST=smtp.provider.tld
35 # Authentication details for your SMTP service
36 MAIL_USERNAME=user@provider.tld
37 MAIL_PASSWORD=onlyifneeded
39 # The "from" email address for outgoing email
40 MAIL_FROM=noreply@yourdomain.tld
42 # The "from" name used for outgoing email
43 MAIL_FROM_NAME=BookStack
48 The `sendmail` drivers uses the sendmail application on the host system. It will call `/usr/sbin/sendmail -bs`.
50 To enable this option you can set the following in your `.env` file:
55 # The "from" email address for outgoing email
56 MAIL_FROM=noreply@yourdomain.tld
58 # The "from" name used for outgoing email
59 MAIL_FROM_NAME=BookStack
64 You can follow the instructions provided in the [debugging documentation page](/docs/admin/debugging/)
65 to help gain more details about issues you may come across. Within the "Settings > Maintenance" area of
66 BookStack you can find a "Send a Test Email" action which provides a quick & easy way to send emails
67 after changing your configuration. This action will also attempt to capture any errors thrown and display them.
73 Webhooks can be configured in the "Settings > Webhooks" area of your BookStack instance.
74 An example of the POST data format is shown when creating or editing a webhook.
76 The running on webhooks can slow down a system due to the required additional processing time.
77 See the [async action handling](#async-action-handling) section below to details on running webhooks
78 in a background process to improve performance.
83 ### Async Action Handling
85 Actions like sending email or triggering webhooks are done synchronously by default within BookStack which can
86 slow down page loading when those actions are triggered. These actions can instead be processed asynchronously
87 so they're handled in the background to prevent slowing down the request. This requires a config change
88 and a queue worker process to handle these background jobs:
92 Within your `.env` file add or update (if already existing) the following option then save the file.
95 QUEUE_CONNECTION=database
98 #### Queue Worker Process
100 The queue work process can be run via the following command from your BookStack installation directory:
103 php artisan queue:work --sleep=3 --tries=3
106 Ideally this needs to be ran continuously. The method of doing this may depend on your operating system
107 and personal software preferences. On many modern Linux systems systemd is an appropriate method.
108 The below unit file example can be used with systemd to run this process. Note, this is suited to
109 Ubuntu 20.04 setups that have used our installation script. Details may need tweaking for other systems.
113 Description=BookStack Queue Worker
119 ExecStart=/usr/bin/php /var/www/bookstack/artisan queue:work --sleep=3 --tries=1 --max-time=3600
122 WantedBy=multi-user.target
125 To configure systemd (On a Ubuntu 20.04 system) with the above unit you'd typically:
127 - Create a new `/etc/systemd/system/bookstack-queue.service` file containing the above content.
128 - Run `systemctl daemon-reload` to discover the new service.
129 - Run `systemctl enable bookstack-queue.service` to ensure the service starts at (re)boot.
130 - Run `systemctl start bookstack-queue.service` to start the queue service.
132 Note: you may need to run the above commands with `sudo` if not acting as a privileged user.
133 You can then use `systemctl status bookstack-queue.service` to check the status of the queue worker.