# Send Paige documents to Salesforce with Zapier or Make

Build the Zap or Make scenario that watches Paige's SFTP export folder, finds or creates the Salesforce record from each document's fields, and attaches the PDF as a File on that record.

Product: paige · Audience: system-administrator · Time: 1 hour · Last verified: 2026-09-05

Canonical: https://help.ademero.com/paige/integrations/send-paige-documents-to-salesforce-with-zapier-or-make

**At the end of this guide, every document Paige finishes becomes — or updates — a Salesforce record within minutes, with the fields filled from Paige's values and the PDF attached to it as a File.**

The automation is: *SFTP trigger → keep only the data file → read the values → find the record (or create it) → attach the PDF.* Paige uploads the PDF before the data file, so the PDF is always there when the automation fires. The example below files a signed customer form against its Account; swap the object and fields for your case.

## Step 1 — Point Paige at your SFTP server

1. In Paige, open **Settings** (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose **Export**.
2. Click the **FTP** card. Enter the **FTP Address**, **Port** `22`, **Username**, **Password**, and in **FTP Folder Path** a folder for this scan job, such as `/paige/forms`.
3. Click **Test Connection**. **What you should see:** `FTP connection successful!` Connect — `Connected to FTP Server!` and a green **Connected** label.
4. Turn on **Enable Auto Export**. Under **Auto Export Settings**, pick the document type under **Document Types**, set **Auto Field Entry Complete** to **Yes**, and set **Human Reviewed** to **Reviewed** if a person should check the values first. Click **Save**.

Open port 22 on your firewall to Paige's address ranges — [Outbound IP ranges for firewall allow-lists](/paige/document-processing/outbound-ip-ranges-for-firewall-allow-lists).

## Step 2 — Build the automation

### Zapier

1. **Trigger:** **SFTP by Zapier → New or Updated File** (connection: **Host**, **Username**, **Port Number** 22, **Password**), folder = the scan job's folder.
2. **Filter by Zapier:** *File Name* **(Text) Ends with** `.json`.
3. **Code by Zapier → Run Javascript**, `file` mapped to the trigger's file:
   
   ```javascript
   const doc = await (await fetch(inputData.file)).json();
   const out = { pdf_file: doc.metadata.pdf_file, document_type: doc.metadata.document_type };
   for (const [k, v] of Object.entries(doc.fields)) out[k] = v;
   return out;
   ```

4. **Salesforce → Find Record.** **Salesforce Object** *Account*; search by *Account Name* = the Paige `Customer Name` field. Turn on the option to create the record if not found, or add a **Salesforce → Create Record** step in a path.
5. **Salesforce → Create Record** (or **Update Record**) for the object that holds the form's data — a *Case*, a custom *Signed Form* object, or the Account itself — mapping each Salesforce field from the Code step's Paige fields, and the lookup to the Account from step 4.
6. **SFTP by Zapier → Download File**, path = the folder plus `pdf_file`.
7. **Salesforce → Create File.** **File** = the download from step 6; **title** = a name built from Paige fields; **Salesforce Object** = the record from step 5, so the File is linked to it.
8. Turn the Zap on.

### Make

1. **SFTP → Watch files in a folder** (connection: **Host**, **Port** 22, **Auth Type** *Username and Password*), pointed at the scan job's folder.
2. Filter: *File name* **Ends with** `.json`.
3. **SFTP → Get a file**, then **JSON → Parse JSON** on its data. Run once with a real file so Make learns the fields.
4. **Salesforce → Search Records** for the parent record; route to **Salesforce → Create a Record** if none.
5. **Salesforce → Create a Record** (or **Update a Record**) with the parsed fields.
6. **SFTP → Get a file** with path = folder plus parsed `metadata.pdf_file`, then **Salesforce → Upload a File** (ContentVersion) linked to the record from module 5.
7. Set the schedule and turn the scenario on.

## Step 3 — Test it

1. Process one document through the scan job in Paige (review it if you required review) and wait for the export.
2. Check the automation's run history: one run, every step green.
3. Open the record in Salesforce. **What you should see:** the fields filled from the document and the PDF under **Files** on the record.

## When it doesn't work

| Symptom | Where to look |
| --- | --- |
| The automation never runs | Wrong folder, or a subfolder. |
| Runs four times per document | The `.json` filter is missing. |
| Find Record finds nothing | The document's name spelling differs from the record. Have Paige's reviewer standardize it, or search on a more reliable key (email, account number). |
| Create Record fails on a field | Type mismatch — a text date into a Date field, or a picklist value that doesn't exist. Convert in a Formatter step or make the field text. |
| File created but not on the record | The **Salesforce Object** link on Create File wasn't set. |
| Nothing arrives from Paige | Auto-export criteria aren't met, or the document was processed before you enabled auto export. Export once from the **Documents** page with **Export** and tick **FTP**. |

If the Paige side is the problem, contact Ademero support with the scan job name and the message from **Test Connection**.

## What's next

- [Connect Paige to Salesforce](https://help.ademero.com/paige/integrations/connect-paige-to-salesforce)
- [Connect Paige to any app with Zapier, Make, or Power Automate](https://help.ademero.com/paige/integrations/connect-paige-to-any-app-with-zapier-make-or-power-automate)