Functionality Reference
  • Resource map
  • Resources
    • Apple Music
    • Auth0
      • Auth0 - API connector's OAuth2 User-Agent Flow.
      • Auth0 - Manual implementation
    • Azure AD SSO
    • Best practices building Bubble.io apps
    • Best practices - Test recommendations for devs
    • Bitly
    • Bottomline BACS payments
    • Bubble API - Authentication
    • Bubble API Connector
    • Check if address is within custom defined area on Map
    • Chrome Devtools
    • Click a button by pressing Enter
    • Credit Card Payments
      • Square
      • Stripe Plugin
      • Stripe Manual Integration
    • Date/Time Operations
    • Dwolla + Plaid ACH
    • Editor.js rich text editor
    • Embedding a pdf preventing the user from downloading it
    • Excel formula parser
    • Exporting data (xlsx, CSV)
    • Documents & eSignatures
      • Eversign
      • Formstack (formerly Webmerge)
      • Hellosign
    • FFMPEG audio processing
    • First Payment Merchant Services
    • Fuzzy Search
    • Google
      • Authentication
      • GA4 Basic implementation
      • Google Analytics
      • Google Calendar
      • Google Charts
      • Google Maps Drawing
      • Google maps geometry - plugin
      • Service Account Authentication
    • How to build quick & safe redirects in Bubble
    • How to correctly use the ID attribute
    • How to secure webhooks
    • Images with text overlays
    • Limit file types in the File Uploader
    • Loading large linked datasets into Bubble
    • Localize Translations
    • Mobile share functionality
    • Nylas
    • OpenAI
    • Paguelo Facil payments
    • PDF generation
    • Perfect Tense (grammar checker)
    • Performance testing
      • Page speed benchmarking
      • App load testing with Loadster
    • Persona ID verification
    • Plaid
    • POST response redirects
    • Postmark (coming soon)
    • QR codes
    • Rappid flowchart
    • Implementing Google reCaptcha
    • Recursive workflows
    • Redirect logged in users from the root domain to the Bubble app
    • Regex
    • S3 plugin
      • UI element
      • No UI element
      • Server-side actions
      • Setting up the AWS bucket
    • Salesforce
    • Security reference
    • Security tools
      • CSV injection prevention
      • Encrypting text
      • File malware scanner
      • XSS stopper + HTML whitelist
    • Sendgrid
      • General info
      • Plugin
    • Simple Marketplace setup with PayPal
    • Stripe no-code portal and Pricing table
    • SVGs
    • Tokbox
    • Tokbox video chat
    • Track users online status
    • Twilio
      • Twilio Studio
      • Twilio SMS
      • Twilio video chat embed
    • Bubble.io Version Control best practices
    • Wistia video player
    • Youtube player and data
    • URL Meta
    • Web3
      • Converting to/from Wei
      • MetaMask Plugin
    • Widget as a service from Bubble as an embedded iFrame
    • Xano: how to implement in Bubble
    • Using the Canvas extension with a non-Canvas app
  • Other
  • Grant access to your Plaid account
  • Grant access to your Twilio account
  • Grant access to your Stripe account
Powered by GitBook
On this page
  • General
  • Spam filter solutions
  • Including a list of things in an email

Was this helpful?

  1. Resources
  2. Sendgrid

General info

PreviousSendgridNextPlugin

Last updated 4 years ago

Was this helpful?

General

To setup SendGrid for your app, please visit

Spam filter solutions

If emails from your app are hitting a spam filter or being blocked by company firewalls, there are a few steps you can take to identify and fix the issue:

  • Authenticate your domain: explaining the process

  • Add DKIM, DMARC, SPF verification: This is done in the DNS settings for the domain. We haven't written up the details but you can flag your PM if you think this is needed.

  • Test your send email: You can to get an email address that you can trigger an email to from your app. You can then refresh the page on the site to get some information on whether the domain is blocked.

Including a list of things in an email

You can see the editor of how to set this up and the preview

The high-level steps are as follows:

  1. Create an HTML field on the object that you want to send in an email. This field should store the HTML code for displaying the contents of the object in the email.

  2. Keep that field updated whenever the object is updated (either through a Custom Workflow or through an API workflow)

  3. When sending an email, populate the contents of all of the matching objects' HTML fields in the body, joined with a blank space

this step in our Canvas Manual.
Here is a short article
go to this site
here
here