Skip to content

Add sendwithus email provider #8625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

scopsy
Copy link
Contributor

@scopsy scopsy commented Jul 1, 2025

%23%23%23 What changed%3F Why was the change needed%3F

Added Sendwithus as a new email provider. This change was needed to expand the range of supported email service providers for users, following the existing patterns for email integrations.

This includes:

  • Core provider implementation (@novu/providers).
  • API and worker support (@novu/application-generic).
  • Dashboard UI configuration (@novu/shared).
  • Unit tests for the new provider.

Relevant documentation: Sendwithus API

%23%23%23 Screenshots

Expand for optional sections

%23%23%23 Related enterprise PR

%23%23%23 Special notes for your reviewer

Copy link

netlify bot commented Jul 1, 2025

Deploy Preview for dashboard-v2-novu-staging canceled.

Name Link
🔨 Latest commit 4e9a76f
🔍 Latest deploy log https://app.netlify.com/projects/dashboard-v2-novu-staging/deploys/68644b249b4a94000857aa6e

Copy link

github-actions bot commented Jul 1, 2025

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Your PR title is: Add sendwithus email provider
It should be something like: feat(scope): Add fancy new feature

Details:

No release type found in pull request title "Add sendwithus email provider". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants