Email Integrations
Send transactional emails through Outlook Mail from your Buildorado workflows.
Email integrations let you send transactional emails directly from your Buildorado workflows. When a form is submitted, a payment is processed, or a specific workflow step completes, you can automatically send confirmation emails, notification emails, follow-up messages, and more. Buildorado offers the Outlook Mail integration for Microsoft 365 environments in addition to the built-in email action powered by Resend.
Outlook Mail
The Outlook Mail integration sends emails from your Microsoft 365 mailbox. This is ideal for organizations that want emails to come from their corporate email addresses rather than a generic sending domain.
Setting Up Outlook Mail
- Navigate to Settings > Integrations in your Buildorado dashboard.
- Find Outlook Mail and click Connect.
- Sign in with your Microsoft 365 account in the authorization popup.
- Grant the following permissions:
Mail.Send-- Send emails on your behalfMail.ReadWrite-- Access mailbox for drafts and sent itemsUser.Read-- Read your profile for sender identityoffline_access-- Allow Buildorado to maintain the connection
- Once authorized, Outlook Mail shows as Connected with your email address.
Operations
sendEmail
Send an email via Outlook.
| Field | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient email address. Separate multiple addresses with commas |
subject | string | Yes | Email subject line |
body | string | Yes | Email body (HTML supported) |
cc | string | No | CC recipients, comma-separated |
Output:
| Field | Type | Description |
|---|---|---|
sent | boolean | Whether the email was sent successfully |
listMessages
List recent email messages from the Outlook inbox.
| Field | Type | Required | Description |
|---|---|---|---|
top | number | No | Number of messages to return (default: 10) |
filter | string | No | OData filter expression |
Output:
| Field | Type | Description |
|---|---|---|
messages | string | Messages as JSON |
getMailFolders
List mail folders in the mailbox. This operation takes no input fields.
Output:
| Field | Type | Description |
|---|---|---|
folders | string | Folders as JSON |
HTML Email Body with Template Variables
Compose the email body in HTML and inject dynamic data from your form submissions:
<h2>New Application Received</h2>
<p>Hello team,</p>
<p>A new application has been submitted with the following details:</p>
<table>
<tr>
<td><strong>Name:</strong></td>
<td>{{applicationForm.fullName}}</td>
</tr>
<tr>
<td><strong>Email:</strong></td>
<td>{{applicationForm.email}}</td>
</tr>
<tr>
<td><strong>Position:</strong></td>
<td>{{applicationForm.position}}</td>
</tr>
</table>
<p>Please review the application in the dashboard.</p>Tips for Outlook Mail
- Emails are sent from the Microsoft 365 account you connected. Make sure this account has a valid mailbox and sending permissions.
- For shared mailboxes, the connected user must have Send As or Send on Behalf permissions.
- Microsoft 365 enforces sending limits (typically 10,000 emails per day for enterprise plans). Check your organization's limits if you expect high volumes.
Common Email Patterns
Confirmation Email on Form Submission
The most common pattern is sending a confirmation email when a user submits a form:
[Form: Contact Request]
-- [Email: Send confirmation to {{form.email}}]
Subject: "We received your request, {{form.firstName}}"
Body: "Thank you for reaching out. We will get back to you within 24 hours."Notification Email to Internal Team
Alert your team when a new submission arrives:
[Form: Support Ticket]
-- [Email: Notify [email protected]]
Subject: "New support ticket: {{form.subject}}"
Body: "Priority: {{form.priority}} | Customer: {{form.email}}"Conditional Email Routing
Use conditional logic to send different emails based on form responses:
[Form: Feedback Survey]
-- Branch: rating
-- rating is 4 or higher -- [Email: Thank you for the positive feedback]
-- rating is 2 or lower -- [Email: We are sorry + escalate to support]
-- else -- [Email: General thank you]Email with File Attachments
When your form collects file uploads, forward those files as email attachments:
[Form: Job Application]
-- [Outlook Mail: Send to [email protected]]
Subject: "Application from {{form.fullName}}"
Attachments: {{form.resume}}Template Variable Injection
Outlook Mail supports the standard Buildorado template variable syntax in all text fields. You can reference any upstream node output:
| Variable Source | Syntax | Example |
|---|---|---|
| Form field | {{formName.fieldKey}} | {{contactForm.email}} |
| Upstream action | {{actionName.property}} | {{stripe_1.paymentId}} |
| Submission metadata | {{submission.property}} | {{submission.createdAt}} |
| Workflow metadata | {{workflow.property}} | {{workflow.id}} |
Variables are resolved at execution time. If a referenced variable does not exist, it resolves to an empty string.
Choosing Between Email Options
| Feature | Built-in Email (Resend) | Outlook Mail |
|---|---|---|
| Send from custom domain | Yes (configured in Resend) | Yes (your M365 address) |
| Visual template editor | No (HTML in workflow) | No (HTML in workflow) |
| Delivery analytics | Basic | Via Microsoft 365 |
| Attachments | Yes | Yes |
| Best for | Quick setup, low volume | Microsoft 365 orgs |
| Limits | Included in plan | M365 limits |
For most use cases, the built-in Resend-powered email action is the fastest to set up. Choose Outlook Mail when you need emails to come from your corporate Microsoft 365 address.