Connect Paige to Salesforce
Two working paths from Paige into Salesforce: an automation on Zapier or Make that creates a record from each document's fields and attaches the PDF as a Salesforce File, or Data Loader for batches — records from Paige's CSV, files from Paige's PDFs. Which to pick, what lands in Salesforce, and the step-by-step guides.
Paige reads the paperwork — applications, signed forms, invoices, handwritten intake sheets — and Salesforce gets a record with the fields filled and the PDF attached as a File, without anyone keying it in.
Salesforce (SFDC, Sales Cloud, Service Cloud) is a database of records, so a Paige integration means two things: create or update a record from the document's fields, and attach the PDF to it. Paige's export gives you both.
What lands in Salesforce
| Zapier or Make | Data Loader | |
|---|---|---|
| A record (Lead, Case, Opportunity, a custom object…) per document | Created within minutes of Paige finishing the document | Created when you run the load, in batches |
| Fields | From Paige's fields, mapped once | From Paige's CSV columns, mapped once in Data Loader |
| The PDF as a Salesforce File on the record | Yes | Yes, in a second load of ContentVersion records |
| Matching to an existing record (by email, account name, …) | Yes — find first, then create or update | Yes — upsert on an external ID |
Pick a path
| Path | Choose it when | Guide |
|---|---|---|
| Zapier or Make | You want records to appear on their own, PDFs attached. Needs a paid Zapier or Make plan. | Send Paige documents to Salesforce with Zapier or Make |
| Data Loader | You load data in batches already and don't want another subscription. Two loads per batch: records, then files. | Load Paige documents into Salesforce with Data Loader |
Developers can also read Paige directly — Integrate your own system with the Paige API — and use Salesforce's REST API (sobjects for the record, ContentVersion with FirstPublishLocationId for the file).