How to Add Attachments in Email

In this document, we will explain how to add a single or multiple attachments in your email.

You can add static as well as dynamic attachments to emails

On clicking on the attach button (highlighted below) on the to right corner of the either Email editor, you will see:

• Upload Files: Allows you to attach files from the system. This then stays as a static attachment in the body of the email and is sent along with the email as an attachment every time it's triggered.

• Dynamic Placeholders: Allows you to include dynamic files within the email, when the notification event is triggered. You can use placeholders to specify the:

  • File Name - Provide a static value like 'Invoice.pdf' (if you are testing it manually) or a placeholder like {{attachment.filename}}(if your are triggering notification event via API)
  • Type - Select the file type from the dropdown or you can enter a placeholder like {{attachment.filetype}} You can see all the MIME types here
  • URL - Provide a static URL or Dynamic URL using a placeholder like {{attachment.presigned_url}}. The URL should be wither pre-signed or public URL.

Placeholders should be used if the attachment information is dynamic (for instance, a personalized attachment depending on the recipient). Typically such attachments are sent via an API call. To send dynamic attachments in the event payload, make sure that the data section of the payload has an object called attachment as shown below.

curl -X POST 'https://api.fyno.io/v1/<WorkspaceID>/event' \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{
    "event": "EmailWithAttachments",
    "to": {
        "email": "xyz@gmail.com"
    },
    "data": {
       "attachment":
        {
            "presigned_URL": "<presigned_URL>",
            "filename": "<attachment_file_name>",
            "filetype": "application/pdf"
       }
    }
}'

In the above command:

How to add multiple attachments?

To add multiple attachments in email, add them in the placeholders as shown below.

Configuring File Attachments Using Fixed Mode

Fixed Mode is used when the number of files is predefined and does not change at runtime.
You manually configure each file (File 1, File 2, etc.) by specifying its name, MIME type, and URL individually.

When to Use Fixed Mode

Use Fixed Mode when:

• The number of files is known in advance.
• The same files are sent to all users.
• Files are static (for example, brochure, invoice template, product catalog).
• You need full control over each file configuration.

Example Static Configuration

File 1

• File Name: invoice.pdf
• MIME Type: application/pdf
• URL: https://example.com/invoice.pdf

File 2

• File Name: coupon.jpg
• MIME Type: image/jpeg
• URL: https://example.com/coupon.jpg

Result:
Both files will always be attached exactly as configured.

Fields Explained

Important Notes

• Each file must be configured separately.
• The URL must be publicly accessible or pre-signed.
• The MIME type must be valid (for example, application/pdf, image/png).
• The number of files will remain fixed for every execution.
• If the file count needs to vary dynamically, use Dynamic Mode instead.

Sample Configuration Summary

If you configure:

Result:
2 files will always be attached:

• product_catalog.pdf
• pricing_sheet.pdf

Configuring File Attachments Using Dynamic Mode

Dynamic mode is used when the number of files is not fixed and is provided at runtime as a JSON array (for example, from a previous step’s output).

Instead of manually adding File 1, File 2, File 3, and so on, you define mappings that tell the system:

“For each item in this array, get the file name from here and the URL from there.”

When to Use Dynamic Mode

Use Dynamic mode when:

• The number of files varies per execution.
• Files come from an API response, loop, or previous ste.
• You don’t know in advance how many files there will be.

Dynamic File Attachment Fields

This section explains all fields used to configure dynamic file attachments.

Important Notes

• Dynamic placeholders must strictly follow the a.0.b format (for example, {{documents.0.name}}).
• The .0. segment is required and acts as a schema hint that allows the system to identify array items.
• Nested arrays or nested objects are not supported.
  If the filename or URL is not a direct property of the array item, dynamic mapping will not work.

Sample Body

{
  "documents": [
    {
      "name": "a.pdf",
      "link": "https://x/a.pdf",
      "mime_type": "application/pdf"
    },
    {
      "name": "b.pdf",
      "link": "https://x/b.pdf",
      "mime_type": "application/pdf"
    }
  ]
}

Dynamic Field Configuration

• File Name (Dynamic): {{documents.0.name}}
• MIME Type: {{documents.0.mime_type}}
• URL (Dynamic): {{documents.0.link}}

Result

Two files are automatically added:

• a.pdf
• b.pdf