On this page
01What it becomes
Server-side calls to the SendGrid API. SendGrid’s actions become server code that calls SendGrid’s REST API with your key from an environment variable. Values that were fixed in Bubble — sender, template ids — stay on the server.
No extra npm package: the generated code uses React, Next.js and browser APIs only.
02What converts
- Send email with dynamic or legacy templates, substitutions, attachments, tracking, unsubscribe groups and scheduled send
- Add a contact to lists
- The plugin’s results (success, errors, message id)
03What you set up
- Set SENDGRID_API_KEY in your hosting’s environment variables.
- Emails sent from page workflows are flagged in your report: Bubble computed recipients and texts on its server, so review who may trigger them.
04About this plugin
SendGrid is made by Copilot / withcopilot.com (API wrapper (server actions)). Bubble’s plugin marketplace counts 54,821 installs (a cumulative counter). See its page on the Bubble marketplace.
Questions
- Does the SendGrid plugin work outside Bubble?
- Not as it is: Bubble plugins only run inside Bubble. In a Next.js app it is replaced by generated code — Server-side calls to the SendGrid API.
- Will my SendGrid settings carry over?
- Yes. deBub reads the plugin’s settings, conditions and workflows from your .bubble export and converts all of the plugin’s parts. Secret keys are the exception: you add them as environment variables.