More reliable loading of the ChiliDocs card
🐛 Bug Fixes
Open the ChiliDocs card even when HubSpot is briefly busy. The card used to fail to load in that moment. It now tries again automatically and loads as expected.
Open the ChiliDocs card even when HubSpot is briefly busy. The card used to fail to load in that moment. It now tries again automatically and loads as expected.
[if …], [elif …], [else] and [endif], for example [if deal.amount >= 10'000 and deal.dealstage = "Closed Won"]. A mistake in the condition shows as SyntaxError right in the document instead of breaking the file.(label) function, for example [deal.dealstage(label)]. It also prints the option label on dropdowns and checkboxes, and works on tickets, orders, courses and custom objects with pipelines.[con-tact.firstname] now shows a SyntaxError in your document and no longer causes failing requests to HubSpot.Generate documents with a table of contents and keep the chapter numbers from your template. The numbering could start at 6 instead of 1. ChiliDocs now only updates the page numbers and leaves the entries as they are in your template.
Name the object in every owner placeholder, for example [contact.owner.hs_email], so a template means the same on every record type. The old names such as [contact.ownerfirstname] and [currentuser.firstname] are retired: ChiliDocs still converts them while generating, but a bare [owner.…] now shows a SyntaxError.
What you need to do
[owner.…] placeholder, e.g. [deal.owner.hs_email].[quote.hs_title].[contact.firstname] [contact.lastname]: each one is filled now.Save your templates as Word .docx files: old .doc files, PDFs or renamed files can't be used. The ChiliDocs card now says so when you pick such a file, workflows stop with a clear error instead of retrying, and the template lists only show .docx files.
Look for ChiliDocs in HubSpot under its new full name, "ChiliDocs - The Smart Document Automation Engine". The card shows the new subtitle. Nothing changes in how you work.
Compare ChiliDocs Free and Pro on the new pricing page, with a feature comparison and billing details. It's linked in the website footer, and old links to the version selection page lead there automatically.
Write download links into properties of custom-object records with the Generate Download Link action. On Enterprise accounts, click Update in the ChiliDocs settings once to approve the permission this needs.
Update ChiliDocs from its settings even if your HubSpot account is hosted in the Asia-Pacific data region. The Update link sent these accounts into an endless sign-in loop. It now always opens the right HubSpot region.
Re-authorize ChiliDocs or upgrade to Pro from a HubSpot account in the EU or another region outside North America. These accounts bounced between HubSpot's sign-in and authorization pages until they were logged out. The links now open the account's own region.
Generate documents directly on custom-object records and get the record's own properties filled in. Until now, every placeholder for the record itself stayed empty there.
Use the new ChiliDocs card for everything: the old ChiliDocs pages and banners inside HubSpot and the classic CRM card are gone. HubSpot no longer supports classic CRM cards, so the new card replaces them completely.
What you need to do
Place dynamic tables such as [line_item_table] inside a cell of another table, for example a layout table. Generating such templates failed with "Invalid document request". The nested table is now filled and your layout stays intact.
Finish a Pro upgrade that a colleague in your HubSpot account already paid for. ChiliDocs asked other users to pay again. It now recognizes the payment for the whole account.
Keep templates for a specific ticket pipeline in a folder named after the pipeline's ID, just like for deals. When you generate from a ticket, ChiliDocs offers the templates from its pipeline's folder, and folders of other pipelines no longer show up on unrelated records.
Install ChiliDocs Pro directly with your installation key, without installing the Free plan first. Open the installation link with your key, approve ChiliDocs in HubSpot, and your Pro plan is set up in one go.
Upgrade to Pro from the ChiliDocs settings in HubSpot again: the upgrade could fail with "upgrade session missing". It now continues in a new browser tab, with a button to reopen it if your browser blocks pop-ups.
Retry an interrupted installation right away. Leftovers from an earlier attempt, for example in another browser tab, no longer block the new one.
Keep access to ChiliDocs when HubSpot has a short hiccup: a failed subscription check no longer locks your account. Accounts that were locked this way recover automatically on the next check.
Reinstall ChiliDocs after a cancelled subscription and start with a clean slate. Settings and data from the old installation are no longer carried over to the new one.
Choose Word as the file type in ChiliDocs workflow actions again. Workflows with this setting stopped with an "unsupported output type" error. They now create the Word document as expected.
Generate a PDF and see it open in a new browser tab right away. If your browser blocks the pop-up, click View PDF in the success message to open it yourself.
Use accented characters like "é" in template and document names. Attached files now keep their name in HubSpot instead of showing a garbled, encoded version.
Use placeholders in your document file names even when some of them are empty. Attached files no longer end up with garbled, encoded names in HubSpot, and your spaces and brackets stay as you typed them.
Limit a table to associations with a specific label, for example [contact_table:Billing contact] … [contact_table_end:Billing contact]. Only records associated with that label appear in the table. Tables without a label work as before.
Filter tables for records where a property is empty, for example [filter(deal.closedate=null)]. Such records are now included instead of being skipped.
Format placeholders in table rows the way you like: bold, colors and fonts now carry over to every generated row. Before, the formatting of table placeholders could get lost.
Install ChiliDocs Free through a new sign-up page that asks for your contact details before you connect your HubSpot account. Your details are transmitted securely, and the rest of the installation works as before.
Install or reinstall ChiliDocs even if its folders already exist in HubSpot Files. The installation progress no longer gets lost during setup, so the page always shows where things stand.
Select your templates once more after this update: ChiliDocs now remembers them by their HubSpot file instead of a link that could expire. Previously saved selections are reset so you no longer run into expired template links.
What you need to do
Keep your templates private in HubSpot Files: ChiliDocs now opens them through short-lived secure links. Your templates no longer need to be public, so search engines can't index them.
Generate documents with a table of contents even when the Word file has small layout irregularities. Updating the table of contents could make generation fail. ChiliDocs now skips what it can't update and still creates your document.
[CurrentHour], [CurrentMinute] and [CurrentSecond].[deal.ownerphone] and [deal.ownerjobtitle] – this works on every object.Put placeholders inside text boxes in your Word templates. ChiliDocs now fills them just like placeholders in the rest of the document.
Open your generated Word and PDF files without errors. A problem with reading the fonts of a template could produce corrupted documents. ChiliDocs now leaves the fonts untouched while loading a template.
Get your generated documents with the right file name. In some cases a document came back with the wrong name.
Keep the formatting of your templates when ChiliDocs fills in placeholders. In some templates, replacing a placeholder broke the surrounding formatting. Fonts, styles and layout now stay as you designed them.
Use tables of associated custom-object records in your templates. These tables did not fill correctly. They now list the associated records as expected.
Add your own phone number and job title to documents with [currentuser.phone] and [currentuser.jobtitle]. They show the details of the HubSpot user who generates the document.
Install ChiliDocs from HubSpot again. A wrong redirect link sent the installation to a development version of the app, so it couldn't finish.
Add (format:removehtml) to a placeholder, for example [deal.description(format:removehtml)], to show rich-text properties as clean text. ChiliDocs removes the HTML tags and keeps spaces and line breaks so the text reads correctly in Word.
Cancel your ChiliDocs subscription directly in the app settings. A paid period stays active until its end, and your cancellation request reaches our support team automatically.
[deal.amount(format:currency)], and get the right result. Some amounts were mistaken for dates and rendered incorrectly.[filter(…)] placeholders again: they were rejected as invalid syntax.Pick from a template list without system folders. Pipeline folders and the folder for attached documents are no longer scanned as general template folders, so their files don't show up by mistake.
Turn multi-value properties into lists again with placeholders like [contact.role(orderedlist)]. These placeholders were briefly not recognized. They are filled correctly now.
Use pipeline-specific templates for deals and tickets again. ChiliDocs didn't find the templates in your pipeline folders. They now appear in the template list as before.
Format numbers exactly as you need with the new formatnumber function, for example [deal.amount(formatnumber:d=2;ds=,;ts=.;c=true)]. Set the number of decimals and the decimal and thousands separators, and add c=true to show the record's currency.
Attach generated Word or PDF documents directly to the HubSpot record you created them from. ChiliDocs saves the file in HubSpot Files and links it to the record, so your team finds it right there.
Use date formats that contain spaces, such as [deal.closedate(format:dd MMMM yyyy)]. Placeholders with these formats weren't recognized before. They now show the date as expected.
SyntaxError in the generated document.[contact.phone(formatphone:prefix)] or [contact.phone(formatphone:noprefix)].format:uppercase or format:lowercase, for example [company.name(format:uppercase)].Show currency amounts with the decimal and thousands separators that are usual for their currency. Amounts in your documents now follow these local conventions instead of one fixed format.
[deal.closedate(format:dd-MM-yyyy)].format: syntax everywhere, including format:%, format:dateonly and format:timeonly.Show only the rows you need in a table by adding a filter, for example [filter(company.city="Winterthur")] or [filter(line_item.quantity=1,line_item.hs_sku="SKL")]. Place the filter inside the table, and ChiliDocs includes only the matching records.
Build tables from associated records such as line items or companies: put a row between [line_item_table] and [line_item_table_end] and fill it with placeholders like [line_item.name]. ChiliDocs adds one table row per record.
Count images from 1 in image placeholders: the first image is now number 1. Before, the numbering was off by one, so a different image than expected could end up in your document.
Insert images into your documents with the (image) function, for example [contact.photo(image)]. ChiliDocs places the image from the property right where the placeholder stands.
Generate documents from contacts, companies and tickets with the new ChiliDocs. Keep your Word templates in HubSpot and fill their placeholders with the record's data.
Show properties with several values as a bulleted or numbered list with (unorderedlist) or (orderedlist), for example [contact.hobbies(unorderedlist)]. Or join the values in one line with a separator such as (commaseparated).
Show the right owner details in your documents. Placeholders that refer to the HubSpot owner are now filled correctly.
Fill placeholders for custom objects in your documents. ChiliDocs now matches the custom object's internal name and prefix correctly, so its values appear where you expect them.