For people who send emails through Pipefy
When sending emails with attachments through Pipefy, the maximum permitted size depends on the type of integration used to send them. Each option, whether Pipefy’s default server, a custom SMTP integration or the Outlook integration, has its own limit. This article explains these limits, how they apply to manual and automated sends, and what to do when you need to share larger files.
This article explains which limits apply to each integration, why they differ and what changes for automated emails.
Manual sends from a card or sends via API
The limit applies to the combined size of all attachments in one email, not to each file individually.
| Sending connection | Total attachment size limit |
|---|---|
| Pipefy default server | 10 MB |
| Custom SMTP (including Gmail, Google Workspace and Microsoft SMTP) | 10 MB |
| Outlook integration | 20 MB |
If the attachment size exceeds the limit for the type of integration used, Pipefy blocks the email before sending it. These limits cannot currently be adjusted for a specific organization.
Attention: The 20 MB limit applies only to the Outlook integration. A regular SMTP integration, even with a Microsoft server, still has a 10 MB limit.
Emails sent by automation
Emails sent by the “Send email template” automation and by tasks do not go through the Pipefy attachment size validation described above. They are subject to the limits of the sending server: Pipefy’s default server, your custom SMTP server or Microsoft.
We recommend keeping attachment size below 10 MB to reduce the risk of delivery failures. Even if your SMTP server accepts larger attachments, the recipient’s email server may have a lower limit and reject the message. This is a recommendation, not a fixed limit for automations or a guarantee of delivery.
Why does the Outlook integration allow larger attachments?
The limit depends on the integration used to send the email. For SMTP integrations, such as Gmail and Google Workspace, the combined attachment limit for manual sends from a card or sends via API is 10 MB. With the Outlook integration, Pipefy delivers the message directly through the Microsoft Graph API. This sending route allows a 20 MB limit.
The difference therefore goes beyond the provider: a Microsoft account connected through SMTP is also subject to the 10 MB limit. The 20 MB limit applies specifically to the Outlook integration.
For manual sends from a card or sends via API, Pipefy checks the attachments before handing the message to the email server. A higher limit at your provider does not change this validation.
For example, a manual email with 12 MB of attachments sent through a Gmail or Google Workspace SMTP integration is rejected by Pipefy because it exceeds 10 MB, even if the provider would accept it.
How to send larger files
- Split the attachments across multiple emails, keeping each email within its applicable limit.
- Share larger files as links through Google Drive, OneDrive or SharePoint. Check that the recipient has permission to access them.
- If you use Microsoft 365, consider the Outlook integration for the 20 MB limit on manual sends from a card or sends via API. See how to connect Microsoft Outlook to Pipefy.
Before moving on, confirm that you understand:
☐ The limit applies to the combined size of all attachments.
☐ The 20 MB limit applies to the Outlook integration through the Microsoft Graph API; a Microsoft SMTP integration still has a 10 MB limit.
☐ You can split files across emails or share them as links.
