Pimberly Document Loader
Pimberly Document Loader brings from Pimberly the products updated since a date and prepares, for each one, a text and a set of product details. You choose which attributes make up the text and which are kept as product details. It can also read the PDF documents linked from the product, such as data sheets or manuals.
Use it to feed a knowledge base with your catalogue, so an assistant can answer questions about your products.
When to use it
- Build a sales assistant that knows the whole catalogue and its features.
- Answer technical questions from each product’s PDF data sheets.
- Update the knowledge base every week with the products that changed.
- Prepare product texts for review or translation.
Configuration
You need a Pimberly API credential with your Pimberly account’s access key. See Credentials.
| Field | What it does |
|---|---|
| Credential (required) | The Pimberly API credential. |
| Since Date | Brings the products updated since this date, for example 2026-01-01. If you leave it empty, it brings those updated in the last week. |
| Text fields separated by comma | The product attributes that make up the text, separated by commas. If you leave it empty, the text includes every attribute, each with its name. |
| Metadata Fields to include | The attributes kept as product details, separated by commas. With *, the initial value, all of them are kept. |
| Metadata Fields to exclude | Attributes you do not want to keep as details, separated by commas. |
| Document Fields to include | The product attributes that hold links to PDF documents, separated by commas. If you fill it in, the component downloads the first PDF it finds in them for each product, and its content becomes the text. |
| Source Field Template | How the source of each text is built, using product attributes in braces, for example https://www.mystore.com/product/{Primary ID}. If an attribute does not exist, the source is set to Pimberly. |
| Split by page | With PDF documents, creates one text per page instead of one per document. Off by default. |
Advanced options
| Field | What it does |
|---|---|
| Max Results | The maximum number of products brought in. Default: 10. |
Output
The Data output returns one item per product, or per document or page if you use Document Fields to include. Each item carries:
text: the product’s or the document’s text.- The attributes you chose as product details.
source: the source, if you set Source Field Template. With documents, it is the PDF’s link, anddocument_type, the attribute it came from, is added too.
Connect the output to the component that stores the texts in your knowledge base.
Example
A home appliance manufacturer wants an assistant that answers with the information in its data sheets.
- Add Pimberly Document Loader and choose the Pimberly API credential.
- In Document Fields to include, enter the name of the attribute where you keep the link to the data sheet.
- In Metadata Fields to include, enter
Primary ID,Titleso each text knows which product it belongs to. - Turn on Split by page if the data sheets are long.
- Connect Data to the component that stores the texts in the knowledge base the assistant uses.
Good practices
- Write attribute names exactly as they appear in Pimberly and without spaces after the commas.
- If you schedule the flow to run every week, leave Since Date empty: each run brings what changed in the last seven days. See Scheduler.
Related components
- Pimberly API: to work with the products as they are, without turning them into texts.
- Pimberly Product Tool: to let an agent look up a specific product.