Purser, by GTM Cloud · Close and renew · Early access

Generate a PDF from a Salesforce record, and see the real file first

Purser handles Salesforce document generation for PDF and Excel. Read in the Word or HTML file your team already uses, map its merge fields, and people generate from the record. They see the real file first, and every document is logged.

You know this one

6:10 pm. The customer wants the quote tonight. The opportunity has the products, the quantities and the total, so you open last quarter’s Word file, save it under a new name, and start typing them in again.

Line three still has the old product name. The total in the document is one digit off from the total in Salesforce. You spot it at 6:40, after the logo has drifted to the right for reasons nobody will ever explain.

It’s a PDF by seven. A month from now, no one can say which version went out. That includes you.

Salesforce document generation from the record, not from memory

Purser makes a PDF or an Excel workbook from any Salesforce record. An admin reads in the Word or HTML file your team already uses and says what each merge field should show. People then generate from the record and see the real file before anything is made.

They can save it to the record, a related record or a library, or email it. Operations can make documents for a list of records in one run.

A purser is the officer who keeps a ship’s papers and accounts. Same job, done from the record.

See it first. Take it back. Keep the receipt.

PreviewUndoProve
The preview is the real PDF, or each sheet of the real workbook.A generated document can be removed again.A log row for every document, with the template version that made it.

What you get

Design it once, from the file you already use

The reader finds every merge field and maps it to a field, a child list, a built-in value or fixed text. A template can’t be saved with one left unmapped. Conditions, totals, calculations and lists inside lists are built in, with eleven starters to copy.

The preview is the real file

For a PDF, you see the PDF. For a workbook, you see each sheet in the template’s own colors. Warnings tell you what was left out.

PDF, Excel and a Word copy

An Excel template builds a branded workbook from a record, a list, a query or a report. A PDF template can also save a Word copy beside it.

Controlled and traceable

Every document is a log row with the template version that made it. Templates can need approval, and a changed template is switched off until it’s approved again.

Safe by construction

Purser runs as the person, in user mode, so a field they can’t read is blank in their document. Values are always plain text, never markup, and an admin’s formula or query is checked against an allowlist.

Ready for agents, when you are

Two Agentforce actions list a record’s templates and make the document, dry run first. They’re off until you turn them on.

How it works

  1. Assign access. Admins get Purser Admin, approvers Purser Approver, and everyone who makes documents Purser User.
  2. Check Settings. Turn it on and add the objects templates may use.
  3. Make a template. Copy a starter, or read in your own Word or HTML file and map its fields.
  4. Put the panel on a page. Add the component to a record page, or the Generate action to an object.

Two readers, two reasons

If you’re the admin

You own the templates, who is offered them, and whether they need approval. Read in the file that exists, say what each field shows, and hand the panel to the people who send it.

If you’re the one signing off

Every quote retyped into Word is a chance for the number to be wrong and the layout to be off-brand. Purser makes the document from the record, the same way every time, and can tell you which template version went to the customer.

Today, and with Purser

TodayWith Purser
Quotes retyped into WordOne template, mapped to the record
Workbooks formatted by hand every weekA branded workbook from a button
No record of which version was sentA log row for every document
Layouts that differ by personA preview before anything is saved

Where it’s strong, and what to know first

We’d rather you find the limits here than after you install.

Where Purser is strong

  • PDF and Excel output from one app, with an optional Word copy beside a PDF
  • The preview is the real file, with warnings that say what was left out
  • Every document is logged with its template version, and can be removed
  • Template approval: a changed template is switched off until it’s approved again
  • It runs as the person, so a field they can’t read is blank in their document

Good to know before you install

  • The Salesforce platform draws the PDF, so templates follow what its PDF engine supports. Check a heavily designed layout in the preview first.
  • Purser makes and sends the document. It doesn’t collect electronic signatures.
  • The Quote starters need Quotes turned on in your org.
  • The Agentforce actions are off until you turn them on.

Questions people ask

How do I generate a PDF from a Salesforce record?

With Purser, you generate it from the record page. An admin reads in your Word or HTML file once and maps its merge fields. After that, anyone with access opens the panel on the record, picks the template, checks the real PDF in the preview, and saves it to the record or emails it.

Do we have to rebuild our templates?

No. Read in the Word or HTML file you already use. The reader finds every merge field, and you say what each one shows. A template can’t be saved with a field left unmapped, so a gap shows up while you build.

Can someone get data they should not see?

No. Purser runs as the person in user mode, so a field they can’t read is left blank in their document and they’re warned. Values are always plain text, never markup or a formula. Nobody gets a document with data they couldn’t already read.

Is this only for PDFs?

No. An Excel template builds a branded workbook from the record, a list, a query or a report, with formulas, totals and print headers. A PDF template can also save a Word copy beside it. One app covers the PDFs and the workbooks your team sends.

Does a document leave our org to be made?

No. The Salesforce platform draws the PDF inside your org, and there is no external service. Templates are Custom Metadata, documents are saved as Files, and the log is an object in your org, so nothing needs to leave it.

Does Purser collect electronic signatures?

Not today. Purser makes and sends the document, but it doesn’t collect electronic signatures. Purser Sign, a planned feature that would let people sign a generated document on the record, is in design and isn’t built yet. You can join the pilot.

Works well with

Purser is part of the Close and renew stage. Pair it with Sistership to clone a renewal first. Rolling out templates across teams? Our Salesforce services can help. Every app installs by itself. None needs another.

Built on the platform

  • Native to Salesforce. Templates are Custom Metadata, documents are Files, and the log is an object in your org.
  • Runs as the person, so nobody gets data they couldn’t already read.
  • Nothing leaves your org. The platform draws the PDF, and there’s no external service.
  • Three permission sets: Admin, Approver and User.

Bring the document you retype every week

Ask for early access and a walk-through with your own Word file turned into a template. Generate it from a record and see the real file before it’s saved.