BulkRender for HubSpot.

BulkRender turns a HubSpot record into a finished document. You build a Word template once and tell BulkRender which HubSpot property fills each placeholder. From then on, every document comes out populated with the right names, dates, and figures, in your layout, ready to send.

There are two ways to generate, and both are live today. You can generate inside HubSpot, where a workflow action creates the document automatically as a step in a workflow, so a closed deal or a new ticket produces its paperwork without anyone opening BulkRender. Or you can generate inside the BulkRender app, where the Generate screen lets you search your CRM, pick the records you want, and produce documents on the spot.

Either way, the setup is the same and you do it once: connect your portal, then map your template's placeholders to HubSpot properties. One BulkRender organization connects to one HubSpot portal.

1. Open Settings, then Integrations.
2. Select Connect HubSpot.
3. Sign in to HubSpot and pick the portal to connect.
4. Review the requested scopes and approve.

HubSpot returns you to BulkRender with the connection listed. BulkRender stores the tokens encrypted and refreshes them automatically.

To disconnect, select Disconnect on the same screen. Disconnecting stops all HubSpot generation, including workflow actions.

BulkRender never requests marketing, CMS, or email scopes.

Custom objects work the same way as standard objects. BulkRender reads your portal's schemas and lists them alongside contacts, companies, deals, and tickets in both the object picker and the field mapping editor.

Two conditions apply:

• Your portal must be on HubSpot Enterprise, which is where custom objects live.
• You must grant the optional crm.objects.custom.read scope. Without it the schemas still list, but record reads fail.

Field mapping tells BulkRender which HubSpot property fills which template variable.

1. Open the template, then Field mapping.
2. Pick the HubSpot object type. Custom objects appear in the same list.
3. Match each template variable to a HubSpot property.
4. Save.

Auto match. BulkRender suggests a property for each variable by comparing names. Check every suggestion before saving.

What maps. BulkRender maps flat, single-value properties: single line text, multi line text, number, boolean, date, dropdown, and owner. Associations, line items, and property history do not map.

What BulkRender tidies for you. When you generate from the app, a few fields are made human-readable automatically. A date becomes a long date, so 2024-03-04 reads as March 4, 2024. An owner becomes a name, so hubspot_owner_id = 12345678 reads as Jane Smith. A dropdown shows its label rather than its internal value. Owner names need the crm.objects.owners.read scope. Note that the HubSpot workflow action inserts these three fields exactly as stored, so if your documents come from a workflow, pre format them in HubSpot.

What stays as stored. Numbers and currency are never reformatted, and totals are never calculated. Store money and any computed value the way you want it to read, for example $1,240.00 rather than 1240, then map that property.

This is the live path. You build it in HubSpot, and it runs in HubSpot. Nobody opens BulkRender to generate a document.

1. In HubSpot, open or create a workflow on a mapped object type.
2. Add an action, then pick BulkRender, then Generate document.
3. Choose the template and the output format.
4. Turn the workflow on.

Behaviour to know:

• Enrolment is blocking. The action waits for the document before the record moves to the next step.
• Repeat protection. BulkRender skips a record that the same template already generated for in the last 7 days.
• Failures continue. If generation fails, the record continues down the workflow rather than stalling. The reason is recorded on the action.
• Credits. A failed generation refunds its credits.

Common failure reasons: no field mapping saved for that object type, the record is missing a mapped property, credits exhausted, or the connection needs reauthorising.

Open BulkRender, go to Generate, and choose the HubSpot tab.

1. Pick an object: contacts, companies, deals, or a custom object.
2. Search your CRM records by name or keyword, and select the ones you want. Up to 100 per run.
3. Choose a template and an output format, then generate.

It uses the same field mapping as the workflow action, so a template set up once works in both places. If writeback is configured, the document link is written back to each record.

Prefer to stay inside HubSpot? Use the workflow action instead.

Writeback puts a link to the finished document into a HubSpot property on the record.

1. In Field mapping, set Writeback property to a single line text property on the object.
2. Grant the matching write scope for that object.

Two limits to plan around:

• The link is a public URL. Anyone holding it can download the document until it expires.
• The document is retained for your organization's retention window, 3 days by default. You can raise this in Settings up to your plan's limit (Pro 30 days, Business 60, Enterprise 90). Past the window the link stops working and the property holds a dead URL.