# Connect Paige to ClickUp

Create a ClickUp task for every document Paige finishes — name, description, and custom fields filled from Paige's extracted values, the PDF attached — with a Zapier Zap or a Make scenario watching Paige's SFTP export folder.

Product: paige · Audience: user · Time: 45 minutes · Last verified: 2026-09-05

Canonical: https://help.ademero.com/paige/integrations/connect-paige-to-clickup

**At the end of this guide, every document Paige finishes becomes a ClickUp task within minutes — named from the document, its details in the description and custom fields, the PDF attached — so whoever owns the next step gets it as work, not as a file in a folder.**

ClickUp has no watched folder, so the route is an automation platform: *SFTP trigger → keep only the data file → read the values → create the task → post the PDF as an attachment.*

## 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/intake`.
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 decide whether to require **Human Reviewed** = **Reviewed**. 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. **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;
   out.summary = Object.entries(doc.fields).map(([k, v]) => `${k}: ${v}`).join("\n");
   return out;
   ```

4. **ClickUp → Create Task.** Pick the workspace, space, folder, and list; **Name** from Paige fields (for example `Invoice INV-20441 – Acme Office Supply`); **Description** = `summary` from step 3; map custom fields from the Code step; set assignee, status, or due date as you like.
5. **SFTP by Zapier → Download File**, path = the folder plus `pdf_file`.
6. **ClickUp → Post Attachment.** Task = the one from step 4; file = the download from step 5.
7. 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; filter *File name* **Ends with** `.json`.
2. **SFTP → Get a file**, then **JSON → Parse JSON** on its data. Run once with a real file so Make learns the fields.
3. **ClickUp → Create a Task** in the list, with the name, description, and custom fields mapped from the parsed fields.
4. **SFTP → Get a file** with path = folder plus parsed `metadata.pdf_file`, then **ClickUp → Upload an Attachment** (attach a file to a task) for the task from module 3.
5. Set the schedule and turn the scenario on.

## Step 3 — Test it

1. Process one document through the scan job in Paige and wait for the export.
2. Check the automation's run history: one run, every step green.
3. Open the list. **What you should see:** a new task with the details in the description and custom fields, and the PDF under attachments.

## 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. |
| A custom field stays empty | Type mismatch — a text date into a date field, or a dropdown value that doesn't exist. Convert, or use text fields. |
| Task created without the attachment | The task ID from Create Task wasn't passed to Post Attachment. |
| 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 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)
- [Connect Paige to monday.com](https://help.ademero.com/paige/integrations/connect-paige-to-monday-com)