npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ayhid/strapi-provider-email-brevo

v3.0.0

Published

Brevo (Sendinblue) email plugin for Strapi v5 with admin panel configuration

Readme

@ayhid/strapi-provider-email-brevo

npm version npm downloads License: MIT Strapi v5

Brevo (formerly Sendinblue) email plugin for Strapi v5 with admin panel configuration.

Features

  • Admin Panel Settings - Configure email settings directly from the Strapi admin
  • Strapi v5 compatible - Built for the latest Strapi version
  • Uses Brevo API - Direct API calls (not SMTP) for faster, more reliable delivery
  • Test Email - Send test emails from the admin panel to verify configuration
  • Development fallback - Logs emails to console when disabled or no API key is configured
  • Full email support - HTML, plain text, CC, BCC, reply-to
  • TypeScript - Fully typed codebase

Installation

npm install @ayhid/strapi-provider-email-brevo

Configuration

Option 1: Admin Panel (Recommended)

After installation, navigate to Settings > Brevo Email in your Strapi admin panel to configure:

  • Enable/Disable - Toggle email sending on/off
  • API Key - Your Brevo API key
  • Default From Email - Default sender email address
  • Default From Name - Default sender name
  • Default Reply-To - Default reply-to address

You can also send a test email to verify your configuration works correctly.

Option 2: Environment Variables

You can also configure the plugin via environment variables. Add to your .env:

BREVO_API_KEY=xkeysib-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[email protected]
BREVO_SENDER_NAME=Your App Name

Then configure in config/plugins.ts:

export default ({ env }) => ({
  'email-brevo': {
    enabled: true,
    config: {
      apiKey: env('BREVO_API_KEY'),
      defaultFrom: env('BREVO_SENDER_EMAIL', '[email protected]'),
      defaultFromName: env('BREVO_SENDER_NAME', 'My App'),
      defaultReplyTo: env('BREVO_SENDER_EMAIL'),
    },
  },
});

Note: Settings configured in the admin panel take precedence over environment variables.

Usage

Sending Emails

Use Strapi's email service:

await strapi.plugins['email-brevo'].services.email.send({
  to: '[email protected]',
  subject: 'Hello from Strapi!',
  text: 'This is a plain text email.',
  html: '<h1>Hello!</h1><p>This is an HTML email.</p>',
});

With CC and BCC

await strapi.plugins['email-brevo'].services.email.send({
  to: '[email protected]',
  cc: ['[email protected]', '[email protected]'],
  bcc: '[email protected]',
  subject: 'Team Update',
  html: '<p>Important update for the team.</p>',
});

Custom Sender

await strapi.plugins['email-brevo'].services.email.send({
  from: '[email protected]',
  fromName: 'Custom Sender',
  to: '[email protected]',
  replyTo: '[email protected]',
  subject: 'Custom sender example',
  text: 'This email has a custom sender.',
});

Admin Panel

The plugin adds a settings page under Settings > Brevo Email where you can:

  1. Enable/Disable the plugin - When disabled, emails are logged to console
  2. Configure API Key - Your Brevo transactional email API key
  3. Set Default Sender - Email and name for outgoing emails
  4. Set Reply-To - Default reply-to address
  5. Send Test Email - Verify your configuration works

Development Mode

When the plugin is disabled or no API key is configured, emails are logged to the console:

[Brevo Email] Plugin disabled - logging email to console
================================================================================
From: [email protected] (My App)
To: [email protected]
Subject: Test Email
--------------------------------------------------------------------------------
Text: This is the email content...
================================================================================

This is perfect for local development without needing a Brevo account.

Getting a Brevo API Key

  1. Sign up or log in at Brevo
  2. Navigate to Settings > SMTP & API
  3. Click "Generate a new API key"
  4. Copy the key (starts with xkeysib-...)
  5. Add it in the admin panel or your .env file

Why Brevo API vs SMTP?

This plugin uses Brevo's Transactional Email API instead of SMTP:

  • Faster - Direct API calls vs SMTP handshakes
  • More reliable - No connection timeouts or limits
  • Better feedback - Detailed error responses
  • Feature-rich - Access to tracking, scheduling, attachments

Requirements

  • Strapi v5.x
  • Node.js >= 20
  • Brevo account (free tier available)

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes using Conventional Commits
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Changelog

See CHANGELOG.md for release history.

License

MIT

Links


Made with love for the Strapi community