---
title: Email
description: Send SAP documents as email attachments. Supports configurable recipients, subject templates, and message bodies with no credential setup required.
type: email
use_cases:
  - Email invoices directly from SAP
  - Notify accounts payable teams with document attachments
  - Send delivery notes and shipping documents to partners
config_fields:
  - name: to
    type: string
    required: true
    desc: "Recipient email addresses (comma-separated for multiple)"
  - name: subject
    type: string
    required: false
    desc: "Email subject line (supports placeholders)"
  - name: body
    type: string
    required: false
    desc: "Email body text (supports placeholders)"
credential_fields: []
---

Send SAP documents as email attachments directly from FileRelay. No credential configuration is needed — FileRelay handles email delivery through its managed sending infrastructure with SPF, DKIM, and DMARC authentication.

## Setup

1. In FileRelay, add an **Email** destination
2. Enter the recipient email address(es) in the **to** field (separate multiple addresses with commas)
3. Optionally customize the **subject** line and **body** text using placeholders
4. Save the destination and attach it to a routing rule

No SMTP server, credentials, or DNS configuration is required.

> **REPLACE:** Screenshot of the Email connector configuration form in FileRelay

## How It Works

When a routing rule triggers, FileRelay composes an email with the SAP document as an attachment and delivers it to the configured recipients. Emails are sent from a FileRelay managed address through authenticated SMTP infrastructure. Delivery status is tracked and visible in the FileRelay activity log.

For documents that exceed the attachment size limit (25MB), FileRelay generates a secure, time-limited download link and includes it in the email body instead of attaching the file directly.

## Configuration

### Recipients

The `to` field accepts one or more email addresses separated by commas:

```
ap-team@company.com, invoices@partner.com, john.doe@example.com
```

All recipients receive the same email with the document attached.

### Subject Line

The `subject` field supports dynamic placeholders that are replaced at send time:

| Placeholder | Description | Example Value |
|------------|-------------|---------------|
| `{doc_id}` | SAP document ID | `4500012345` |
| `{doc_type}` | Document type | `Invoice` |
| `{repo_name}` | Repository name | `Vendor Invoices` |
| `{fileName}` | File name with extension | `4500012345.pdf` |
| `{date}` | Current date (YYYY-MM-DD) | `2026-04-04` |

**Example subject:**

```
SAP {doc_type} {doc_id} from {repo_name}
```

Renders as: `SAP Invoice 4500012345 from Vendor Invoices`

If left empty, FileRelay uses a default subject: `FileRelay: {fileName}`

### Body Text

The `body` field supports the same placeholders as the subject. If left empty, FileRelay includes a default message with the document name, type, and source repository.

## Attachment Details

| Property | Details |
|----------|---------|
| File name | Original SAP document name with extension |
| MIME type | Set automatically based on document format (PDF, XML, TIFF, etc.) |
| Size limit | 25MB as attachment; larger files sent as download links |
| Encoding | Base64 (standard email attachment encoding) |

## Email Deliverability

FileRelay sends emails through managed infrastructure with full email authentication:

| Protocol | Purpose |
|----------|---------|
| SPF | Authorizes FileRelay's sending servers for the sender domain |
| DKIM | Cryptographically signs emails to prevent tampering |
| DMARC | Aligns SPF and DKIM for receiving server validation |

These protocols ensure high deliverability and prevent emails from being flagged as spam.

## Tips

- **Allowlisting** — If recipients report that FileRelay emails land in spam or quarantine, ask them to add the FileRelay sending domain to their email allowlist or safe senders list.
- **Multiple recipients** — All recipients see each other's email addresses (similar to the "To" field in regular email). For privacy, create separate Email destinations for each recipient.
- **Delivery tracking** — Email delivery status (sent, delivered, bounced) is tracked in the FileRelay activity log. Failed deliveries are retried automatically with exponential backoff.
- **No reply handling** — Emails are sent from a no-reply address. Include a contact address in the email body if you want recipients to be able to respond.
- **Large documents** — Documents exceeding 25MB are delivered via secure download links that expire after a configurable period. Recipients click the link to download the file.
- **Compliance considerations** — Email content, including attachments, may traverse public internet infrastructure. For sensitive or regulated documents, consider using an encrypted storage connector (e.g. SharePoint, Box) with a sharing notification instead.
- **Rate limits** — FileRelay enforces sending rate limits to maintain deliverability reputation. For very high-volume email delivery, contact FileRelay support to discuss your requirements.