How do I attach a PDF generated via an HTTP Request node to an Airtable record?

Below is some guidance on how you can upload a PDF generated with an HTTP Request node to Airtable.

---

Understanding the Challenge

Airtable’s API requires that attachment fields receive files as an array of objects where each object contains a URL (and optionally a filename). In your workflow the HTTP Request node returns a binary file (the PDF). Because Airtable cannot directly accept binary data as an attachment, you have two main options:

1. Upload the File to a Hosting Service First:
   Upload the binary PDF to a service that can store files and provide a public URL (for example, AWS S3, Dropbox, Google Drive, or any other file host). Once you have a public URL for the PDF, you can map that URL to your attachment field in Airtable.

2. (If Supported) Use n8n’s Binary Data Mapping:
   In some cases, if the integration supports it, you might pass binary data from one node to another. However, for Airtable and its attachment fields, you ultimately need a URL. (Airtable’s API will look for an object like { "url": "https://..." } rather than raw binary data.)

---

Suggested Steps to Make It Work

1. Upload the PDF to a Hosting Service:
   Add a node right after your HTTP Request that can take the binary file and upload it to a file hosting service. For example, if you have a Dropbox or S3 node available, configure it to receive the binary data. Make sure that the file gets stored somewhere publicly accessible (or at least accessible by Airtable).

   – When the file is uploaded, the hosting node should return a URL to the file.

2. Prepare the Airtable Record:
   In your Airtable node (or even via a Set node beforehand), format the attachment field. The field should be set up as follows:

   JSONCopied
   [
     {
       "url": "={{$json[\"uploadedPdfUrl\"]}}"
     }
   ]

   Make sure that:

   • The Airtable table has an attachment field.
   • You pass the URL (from the previous upload node) in the expected format.

3. Update Your Workflow:
   Replace (or extend) your current Set node so that, aside from setting any text fields (like the email), you also add the attachment field that contains the public URL for the PDF.

   For instance, if your file hosting node returns the URL in a field called uploadedPdfUrl, you’d set your field like this:

   JSONCopied
   {
     "attachment": [
       {
         "url": "={{$json[\"uploadedPdfUrl\"]}}"
       }
     ],
     "Email": "=user@test.com"
   }

   Then connect that data to the Airtable node using the Append operation.

---

Final Remarks

• Direct binary transfer isn’t supported for Airtable attachments.
  You must supply a valid URL.
• Check the mapping mode in your Airtable node.
  Make sure it’s set to map fields automatically or add a custom mapping for your attachment field.
• Review the Airtable API docs to see how attachments should be formatted if you run into any issues.

By following these steps—uploading the PDF first to generate a URL and then passing that URL in the correct format—you should be able to successfully attach your generated PDF to a record in Airtable.

Below is some guidance on how to get your PDF file from the HTTP Request node through to Airtable:

1. Preserve the PDF Binary Data

Your HTTP Request node is configured to return the PDF file as binary data. In your workflow, you have a Set node with the option "keepOnlySet" enabled. This discards any data that isn’t explicitly set—including the binary PDF data.

Solution:
Either disable keepOnlySet so that the binary data remains, or explicitly re-add the binary property in the Set node. For example, if your HTTP Request node outputs the binary data with the property name “data”, you can add an assignment in the Set node which looks like:

JSONCopied
{
  "name": "data",
  "value": "={{ $binary.data }}",
  "type": "binary"
}

This ensures that the binary PDF from the HTTP Request is kept in your workflow output.

2. Mapping the File to Airtable

In Airtable, file attachments are stored in fields that accept an array of objects (each with a URL or base64 encoded file). When using the Airtable node with the “append” operation, you can map your binary PDF field to the corresponding attachment field. Make sure that:

• Your Airtable table has a field configured to accept attachments.
• In the Airtable node’s mapping, reference the binary data property. For example, if your attachment field in Airtable is named “Attachment” and the binary property is called “data”, you can set it like:

JSONCopied
{
  "Attachment": "={{$binary.data}}"
}

If you’re using the “Map Automatically” mode, ensure that your field names in Airtable match the property names output by your previous node. Otherwise, add a manual mapping.

3. Adjusting Your Workflow

Taking your provided workflow as a reference, you might adjust it as follows:

• Remove or adjust the Set node:
  Either remove the Set node if it isn’t needed (since it removes the binary) or configure it to include the binary data from the HTTP Request node.

• Configure the Airtable node:
  In the Airtable node, set the field that accepts attachments to reference your binary data. For example, if the field is named “Attachment” and the binary property is still "data", then in the Airtable node’s Options you would supply:

  JSONCopied
  {
    "Attachment": "={{$binary.data}}"
  }

Summary

1. Ensure the PDF binary data isn’t lost—either by not using “keepOnlySet” or by including the binary property in your Set node.
2. Map the PDF file from the binary property (e.g. “data”) to a file attachment field in your Airtable node.
3. Verify that your Airtable table’s column is set up to accept attachments.

With these changes, your workflow should successfully upload the generated PDF to Airtable.