Plunk
Plunk email provider
@piksail/strapi-provider-email-plunk
Strapi email provider for Plunk
Installation
# using yarn
yarn add @piksail/strapi-provider-email-plunk
# using npm
npm install @piksail/strapi-provider-email-plunk --saveConfiguration
| Variable | Type | Description | Required | Default |
|---|---|---|---|---|
| provider | string | The name of the provider you use | yes | |
| providerOptions | object | Provider options | yes | |
| providerOptions.apiKey | object | Plunk api key. Please refer to @plunk/node | yes | |
| providerOptions.baseUrl | object | Plunk base url if self-hosting. Please refer to @plunk/node | no | |
| settings | object | Settings | no | {} |
| settings.defaultFrom | string | Default sender mail address | no | undefined |
| settings.verbose | string | Print detailled logs. Does not print Authorization header. Use with caution, might leak sensitive data in logs | no | false |
:warning: The Shipper Email (or defaultfrom) may also need to be changed in the
Email Templatestab on the admin panel for emails to send properly
Example
Path - config/plugins.js
1module.exports = ({ env }) => ({
2 // ...
3 email: {
4 config: {
5 provider: "@piksail/strapi-provider-email-plunk",
6 providerOptions: {
7 apiKey: env("PLUNK_API_KEY"),
8 baseUrl: env("PLUNK_BASE_URL"), // Optional, use if self-hosting. Must not contain any path, ex: https://plunk.example.com
9 },
10 settings: {
11 defaultFrom: "john@example.com",
12 verbose: false, // Use with caution, might leak sensitive data in logs
13 },
14 },
15 },
16 // ...
17});Troubleshoot
Turn on verbose for easier debugging.
Couldn't send test email: Unknown route. Check your baseUrl setting, it should look like this: https://plunk.example.com.
Install now
npm install @piksail/strapi-provider-email-plunk
Create your own plugin
Check out the available plugin resources that will help you to develop your plugin or provider and get it listed on the marketplace.