Enveloop Docs
Sign up for Enveloop!
  • Enveloop Docs
  • Overview
    • ✨Features
  • Getting Started
    • Introduction to Enveloop
    • Creating a Template
    • Formatting / Dynamic Content
    • Sending a test message
    • Adding a Sending Domain
    • Deploying your first message
  • Product Guides
    • Elements
      • 🔋Table
    • Using Shared Sections
    • Markdown for Formatting
    • Mustache for Dynamic Content
    • Creating a Verified Sender
    • Logging
    • Monitoring
    • Webhooks
    • Themes
  • Integrations
    • Do I need integrations?
    • SMS Integrations
      • Twilio
      • TextGrid
    • Email Integrations
      • SendGrid
      • Postmark
      • Mailgun
      • Amazon SES
      • SMTP
        • ✉️Amazon SES
        • ✉️Gmail SMTP
        • ✉️Google Domain SMTP Relay
    • Partner Integrations
      • Fly.io
  • Enveloop API
    • Getting Started with Enveloop API
    • Core API Endpoints
      • Connecting to the Enveloop API
      • POST /messages
      • GET /templates/:slug
    • Languages and Frameworks
      • 🟢NodeJS
      • 🏮Ruby on Rails
      • 🟡Python
      • 🏮Ruby
  • Settings
    • Sending IPs
  • Company
    • About Us
    • 👩‍⚖️Terms of Service
    • 😎Privacy Policy
Powered by GitBook
On this page
  • Teams
  • Projects
  • Templates
  • What's Next
  1. Getting Started

Introduction to Enveloop

Enveloop allows you to design and send transactional email and SMS messages.

Last updated 7 months ago

Enveloop helps you easily create, send, and keep track of the messages you generate from your apps. Once you sign up, it only takes a couple of minutes before you can start sending messages, either as test messages from Enveloop, from HTTP/cURL commands, or directly from your app.

Enveloop's organizational structure is simple. It consists of: Teams, Projects, and Templates. When you sign up, we have you create your first Team and Project. All that's left is for you to create your first template.

Teams

Teams are simply a way to manage user access. You can invite one or more people to a team and they have access to all projects assigned to that team. You can create all the teams you need.

Projects

Projects map 1-to-1 to your app. You create a project for each app that needs to talk. Each project contains message templates, dedicated API tokens for your app to use, and Integration settings for the types of messages you need to send.

Templates

Message templates contain both the design and the content (static & dynamic) for the messages that you need to send.

You can add multiple templates, and within each template, you can preview how your message will be rendered, send test messages, and access code snippets that are auto-generated based on the dynamic content you want to use (via ).

Inside each template, you have common elements (ex: text, buttons, headers, etc.). Those elements can be grouped into sections. Sections provide additional styling (padding, margins, colors).

Frequently used sections can be saved as shared sections. This provides you the ability to build custom snippets and consistently display them across multiple message templates.

What's Next

Now that you know the basics, you can . It only takes a couple of minutes!

Mustache
create and send your first template