Quable PIM

Quable is a PIM and DAM for product content. Agents sync a storefront catalog from the PIM incrementally, enrich documents, variants and assets, run import and export profiles, and react to workflow steps and asset changes in real time.

1 trigger 126 actions API key available

Quable PIM website Platform Documentation Capability data verified 2026-08-26

On Quable Event fires when a document moves onto the final workflow step

Agent reads the document with Get Document once per active locale

Agent compares the filled attributes against the completeness setting for that document type

Agent calls Create Predefined Value so a new supplier color is admitted rather than rejected

Agent publishes the finished record to the storefront and records the run with Update Key Value

Agent lists the records it could not finish, naming the attribute and the locale that is empty

The catalog owner decides which products ship short and which wait for the missing translation

What This Integration Enables

Quable is where product content becomes true before it is true anywhere else, and this connector goes further than most catalog integrations because it does not stop at the values. Most product connectors let an agent edit a description or a price. This one exposes the data model itself. Attributes, attribute sets, attribute groups, predefined values, classifications, catalogs, document types and locales are all writable. So are the import and export profiles and schedules that move content in bulk, and the workflows and completeness settings that decide when a product counts as finished.

An agent here is not just filling fields. It can build the shape of the catalog, run the pipeline that populates it, and read back what actually changed. Quable calls a product a document, and a document carries variants, assets and the links that join all three, which puts the DAM half of a product in the same place as the PIM half. That reach is also the reason the human-in-the-loop line on this page sits at the data model rather than at the content. Writing a description is recoverable. Removing the field the description lives in is not.

Without FlowRunner

Enrichment by spreadsheet Product copy moves between the PIM and a shared sheet, and the sheet is the version people trust

Locales finished last The primary language goes live and the others catch up whenever someone has an afternoon

Model changes by ticket Adding an attribute or a select option means a request to whoever administers the PIM

With FlowRunner

Enrichment as a running process Agents read, fill and validate documents continuously, and the PIM stays the version people trust

Locales tracked per language Completeness is measured per locale, and the gaps arrive as a list rather than a surprise

Model changes as workflow steps Attributes and select options are created from a flow, and only the destructive ones wait for a person

Use Case Scenarios

The storefront catalog that stays current on its own

The On Quable Event trigger fires on a document update. The agent re-reads the record with Get Document in each active locale, pulls its packshot through the links with List Links, and pushes the result to Shopify or Magento. A scheduled sweep covers anything the webhook missed, using List Documents filtered on modification date with the cursor kept in Quable's own key value store. Nobody exports a CSV, and the storefront and the PIM stop disagreeing about what a product is called.
Bulk enrichment that runs as a job, not a loop

A supplier drops a price and content file. Rather than looping Create Document row by row, the agent reads the sheet from Google Sheets, maps it against Get Document Type Attributes, and drives the load through Create Import Profile and Create Import Schedule so Quable does the ingestion. Because imports are asynchronous, the agent then polls List Processes and Get Process, or waits for the import finished event on the trigger, before it tells anyone the load succeeded. A job that half ran is reported as half run.
The schema audit that ends at a person

On a schedule, the agent walks List Attributes, then counts real usage per attribute across every document type and every locale, checks which export profiles reference each one, and assembles the evidence. It posts the candidates to the catalog owner in Slack with the counts attached. The agent does not delete anything. It creates and updates attributes freely, and it hands the removals to the person who knows what the spring catalog still needs.

Human-in-Loop Highlight

Delete Attribute removes every value stored under that attribute across the whole instance, in every locale, on every document, and there is no recovery. Quable answers with an empty body, so the agent does not even receive a report of what it destroyed. The realistic failure is specific. An agent running a tidy-up query decides an attribute is unused because it is empty in the locale it sampled, when it is populated in another language, or on a document type nobody has touched this season, or read by an export profile that only runs at catalog time. Delete Predefined Value has the same shape one level down, because documents holding that choice lose the value.

So the agent does the work that scales and stops before the work that cannot be undone. It posts: "Attribute care_instructions is empty on all documents in en-US, populated on many in de-DE, and named in the wholesale export profile. Delete it, or leave it?" The catalog owner answers. Creating attributes, updating them, filling them and reporting on them is ordinary automation. Destroying a column of the catalog is a decision with a name on it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

126 actions

Documents

List Documents Search products with filters for document type, catalog, classification, workflow step, tag, activity and modification date. The read behind every incremental sync.
Get Document Read one document with its attribute values, classification, type and links. Pass a locale to get one language rather than every translation.
Create Document Create a product under a document type with its classification, attribute set and values.
Update Document Change a document's identifier, classification, attribute set, activity or values. Only the attributes named in the payload are touched.
Delete Document Permanently removes a document with its values and its links, and reports the identifier it deleted.

Variants

List Variants List the size, color or packaging declinations of your products, filtered by document, catalog, classification, workflow step or modification date.
Get Variant Read one variant with its attribute values and the document it belongs to.
Create Variant Add a declination to a product.
Update Variant Change a variant's identifier, parent document, activity or values, touching only the attributes named.
Delete Variant Permanently removes a variant and its values.
Duplicate Variant Copy an existing variant with its parent and its values. The fastest way to add another size to a product that already has one.

Assets

List Assets List the digital assets in Quable's DAM, filtered by catalog, classification, tag, file name or modification date.
Get Asset Read one asset with its values, classification, file and the renditions its thumbnail profiles produce.
Create Asset Register a DAM asset around a file already uploaded, or around a remote URL when the bytes stay outside Quable.
Update Asset Change an asset's name, classification, activity, values or the file behind it. Replacing the file changes the image everywhere the asset is linked.
Delete Asset Permanently removes an asset and detaches it from every document, variant and classification that linked to it.
List Files List the raw stored files, which are the bytes assets and imports point at rather than the assets themselves.
Get File Read one file record with its original name, mime type, size and serving URL.
Upload File Fetch a file from a URL and store it in Quable, returning the record Create Asset takes. The first half of adding media to the DAM.
List Thumbnail Profiles List the rendition recipes the instance applies to every asset. Their identifiers are the keys the rendition URLs are published under.
Get Thumbnail Profile Read one thumbnail profile with its dimensions, format, resizing operation and filling color.

Classifications and Catalogs

List Classifications List the nodes of a catalog's category tree, filtered by catalog or modification date. Each row names its parent, so the tree rebuilds from one flat page.
Get Classification Read one classification with its parent, its assignment mode and its own values.
Create Classification Add a node to a category tree, optionally under a parent, choosing whether documents are filed by hand or by rule.
Update Classification Rename a node, move it under a different parent, change how documents are assigned, or set its values. Moving a node takes its subtree with it.
Delete Classification Removes a node from the tree. Check its children first, because everything filed beneath it is affected.
List Catalogs List the catalogs on the instance. A catalog scopes a classification tree, a set of attributes and a set of link types, so it is usually what separates one channel or market from another.
Get Catalog Read one catalog with its name, description and the kind of record it holds.
Create Catalog Create the scope a classification tree, attribute set and link types belong to. Setup work.
Update Catalog Change a catalog's name or description. What it holds is fixed at creation.
Delete Catalog Removes a catalog along with the tree, attributes and link types scoped to it. Among the most destructive calls the API offers, and a natural second candidate for a human gate.
Get Catalog Classification Tree Read one catalog's classifications as a nested tree from a chosen node and depth. The operation to use when mirroring a category structure into another system.

Data Model

List Attributes List the data model's attributes with their value types and flags, filtered by document type, attribute set, catalog or type. This is what tells a flow which keys a document may carry.
Get Attribute Read one attribute with its value type, flags, localized labels and the sets it belongs to.
Create Attribute Add an attribute to the model, choosing its value type, labels, group and sets, and whether it is required, filterable, visible or computed.
Update Attribute Change an attribute's labels, group, sets and flags. The value type is fixed, and the set list replaces rather than adds.
Delete Attribute Removes an attribute and every value stored under it across the instance, with no recovery. The operation this page's human gate exists for.
List Attribute Sets List the named bundles of attributes that decide which fields a document carries. An attribute set is what makes one product a shoe and another a fragrance.
Get Attribute Set Read one attribute set with its document type, labels and bundled attributes.
Create Attribute Set Create the field bundle documents of a type will carry.
Update Attribute Set Change a set's labels or its attributes. Removing an attribute hides its values on every document using that set.
Delete Attribute Set Removes a set, so documents built around it lose their field bundle. Check what uses it first.
List Attribute Groups List the headed sections attributes are arranged into on the editing screen. Presentation rather than storage.
Get Attribute Group Read one attribute group with its localized name and its parent.
Create Attribute Group Create a headed section on the document editing screen for attributes to be assigned to.
Update Attribute Group Change a group's label or move it under a different parent. Groups can be renamed but not removed through the API.
List Predefined Values List the allowed choices behind select attributes. Filter by attribute to read one dropdown rather than all of them.
Get Predefined Value Read one predefined value with its attribute and its localized labels.
Create Predefined Value Add a choice to a select attribute. This is how a new supplier color gets admitted automatically instead of failing the import row.
Update Predefined Value Change a value's identifier or labels. Relabeling is safe because documents store the identifier. Renaming the identifier is not.
Delete Predefined Value Removes a choice, and documents currently holding it lose the value. Gated alongside Delete Attribute for the same reason.
List Document Types List the families of records the instance holds, such as products, packagings or marketing assets, and whether each supports variants.
Get Document Type Read one document type with its localized name, whether it is the default and whether its records may have variants.
Get Document Type Attributes Read a document type's attributes as a tree by group and set. The single call that describes everything a document of that type can hold, and the right place to build a field mapping before writing anything.
List Locales List the locales the instance runs, with their fallbacks and whether each is active. These identifiers key every localized value.
Get Locale Read one locale with its fallback and its active state.
Update Locale Activate or deactivate a locale and set what it falls back to when a translation is missing. The available set is fixed by the instance.
List Tags List the free labels documents, variants and assets can carry. Document searches can filter on them.
Get Tag Read one tag with its localized labels. Tags are managed in the PIM interface and only read here.

Data Flow

List Import Profiles List the saved recipes describing a file's format, its column mapping and the locales it carries. For bulk loading, prefer these over looping single document writes.
Get Import Profile Read one import profile with its format settings, mappings and locales.
Create Import Profile Create the recipe that tells Quable how to read a supplier file and which column feeds which attribute.
Update Import Profile Change a profile's name, format, locales or mapping. Mapping and locale lists replace rather than merge, so send them whole.
Delete Import Profile Removes an import profile, which stops any schedule that runs it.
List Export Profiles List the saved recipes describing what to extract, from which catalog, in which column layout and which locales.
Get Export Profile Read one export profile with its catalog, filters, joins, mappings and locales.
Create Export Profile Create the recipe that decides what Quable extracts and how. For moving many records out, this beats paging the document list.
Update Export Profile Change an export profile's name, catalog, filters, joins, locales or layout. Mapping and locale lists replace rather than merge.
Delete Export Profile Removes an export profile, which stops any schedule that runs it.
List Import Schedules List the scheduled imports, each pairing profiles with a cron expression and a timezone.
Get Import Schedule Read one import schedule with its profiles, cron expression, timezone and status.
Create Import Schedule Set a recurring supplier load running on a cron expression, so no flow has to poll for it.
Update Import Schedule Change a scheduled import's name, profiles, cron expression, timezone or status. Changing status pauses a load without losing its configuration.
Delete Import Schedule Removes a scheduled import and leaves the profiles it ran in place.
List Export Schedules List the scheduled exports, each pairing profiles with a cron expression and a timezone.
Get Export Schedule Read one export schedule with its profiles, cron expression, timezone and status.
Create Export Schedule Set a recurring feed running on a cron expression. Pair it with the export finished event so a flow reacts the moment the file is ready.
Update Export Schedule Change a scheduled export's name, profiles, cron expression, timezone or status.
Delete Export Schedule Removes a scheduled export and leaves the profiles it ran in place.
List Processes List the import and export jobs with their status, source and timing. Because bulk work is asynchronous, this is how a flow learns it finished rather than assuming it did.
Get Process Read one job with its per step status and the files it produced or consumed. The polling half of the asynchronous contract.
List Events List the entries in Quable's own webhook event log. Use it to audit what a webhook should have delivered when a trigger looks like it missed something.
Get Event Read one event log entry with the events it carried and the resources they referred to.

Workflow and Completeness

List Workflows List the workflows on the instance, each being the steps and transitions a document type moves through on its way to publication.
Get Workflow Read one workflow with its steps, transitions and document type.
Create Workflow Create a workflow for a document type with its steps and the transitions between them.
Update Workflow Change a workflow's labels, steps or transitions. The lists replace what is there, and a document sitting on a removed step is left with nowhere to go.
Delete Workflow Removes a workflow with its steps and transitions, so documents sitting on one of them lose their position in the process.
List Workflow Steps List the workflow steps across the instance. These identifiers are what a document search filters on, so this answers which products are waiting at which stage.
Get Workflow Step Read one step with its labels and its workflow.
List Workflow Transitions List the permitted moves between steps and the conditions attached to them.
Get Workflow Transition Read one transition with the steps it moves between and its conditions.
List Completeness Settings List what each document type must fill before it counts as ready. Completeness is the number a PIM rollout gets measured on.
Get Completeness Setting Read one completeness setting with the fields, attributes and link types it requires.
Create Completeness Setting Define what a document type must carry to count as complete. Requiring a link type is how a rule such as no publication without a packshot gets enforced.
Update Completeness Setting Change the rule. Tightening it makes documents that were complete yesterday incomplete today, which is exactly what a publication gate keyed on completeness will notice.
Delete Completeness Setting Removes the rule, and the ratio disappears from every document of that type, so anything filtering on it stops matching.

Utility

List Key Values List the instance's key value store, which is a convenient place for a flow to keep its own state such as the last successful sync timestamp.
Get Key Value Read one entry with its value and its protected and public flags.
Create Key Value Store a value in the scratchpad. Do not set the protected flag on anything a flow will need to write again.
Update Key Value Change a stored value. An entry created as protected refuses this call, which is what the flag is for.
Delete Key Value Remove an entry from the key value store.
List AI Templates List the prompt templates saved on the instance, which are what Quable's own generation features run against product data.
Get AI Template Read one template with its code and prompt text.
Create AI Template Save a prompt template the instance's generation features can run.
Update AI Template Change a template's code or prompt text. Templates can be rewritten but not removed through the API.

Webhooks

List Webhooks List the webhook configurations on the instance, including the one the trigger registers for itself. A safe connection test, since it needs only a read token.
Get Webhook Read one webhook with its URL, event list and the headers Quable sends with every delivery.
Create Webhook Register a webhook delivering chosen events to an endpoint outside FlowRunner. Inside FlowRunner, the trigger manages its own.
Update Webhook Change a webhook's name, endpoint, events, headers or delivery state. Event list and headers replace rather than merge.
Delete Webhook Removes a webhook configuration. Deleting the one the trigger registered stops that trigger firing with no other sign.

Legacy

List Unclassified Documents (Legacy) Return the documents filed in no classification at all, which the current API offers no way to ask for. The standard data quality sweep after an import, because an unclassified product is invisible in every catalog tree.
Assign Workflow Step (Legacy) Force a document onto a workflow step. This is the only way to move a document through a workflow from the API, and it does not check that a transition into that step exists.
Remove Workflow Step (Legacy) Take a document off a step. A document with no step is outside the process rather than back at the start of it, so pair this with the assignment when moving one.
List Downloads (Legacy) List the files Quable prepared for the token's own user, which is where an export lands when it is generated for download rather than pushed.
Get Download (Legacy) Read one prepared download with the location its bytes can be fetched from. The item has to belong to the user the token authenticates as.

Triggers

1 triggers

Event Triggers

On Quable Event One realtime subscription covering every change Quable publishes. A document, variant, asset, link, classification or predefined value created, updated or deleted, and an import, export or bulk edit finishing, all arrive on the same trigger. Choose the specific event names a flow cares about, or a group that expands into them, and FlowRunner registers and removes the webhook for you.

Frequently Asked Questions

What can FlowRunner do with Quable PIM?

FlowRunner agents can run List Documents, Get Document, and Create Document in Quable PIM, plus 123 more actions.

Does connecting Quable PIM to FlowRunner require OAuth?

No. Quable PIM connects to FlowRunner with an API key, no OAuth flow required.

Can Quable PIM trigger a FlowRunner workflow automatically?

Yes. Quable PIM supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Quable PIM

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us