Skip to main content

Catsy Category to iPaaS.com Mapping Documentation

How Catsy categories and collections are transferred into iPaaS.com as categories, including field mappings, ID format, and prerequisites.

Overview

This mapping documentation describes how Catsy category data is transferred into iPaaS.com. The Add/Update Catsy Category TO iPaaS.com collection creates or updates iPaaS.com Category records from two kinds of Catsy taxonomy — Catsy Categories and Catsy Collections — so the iPaaS.com catalog structure mirrors how products are organized in Catsy.

Catsy organizes products under both categories and collections, and this collection handles both. A record's type is identified by the prefix on its ID — Cat for a category and Col for a collection. Categories are hierarchical and keep their own parent; collections are flat and are placed under a default parent category.

ID Format

For Manual Sync, enter the full Catsy ID including its type prefix — Cat for a category (for example, Cat4000696937) or Col for a collection (for example, Col4000012345). The prefix is case-sensitive; an ID that does not begin with Cat or Col is rejected.

After a successful transfer, iPaaS.com saves the Catsy ID as the external ID on a dedicated external-ID record for the category. Subsequent transfers use that link to route updates to the same iPaaS.com Category rather than creating a duplicate. On first sync, when no external-ID record exists yet, a Category with a matching Name is linked instead.

Mapping Collection Status

Enabled. This collection has no mapping filter, so all Catsy category and collection records are processed.

Supported Child Collections

None. A category is transferred as a single record with no dependent child collections.

System Caveats

Catsy Caveats

  • Type prefix: category IDs begin with Cat and collection IDs with Col. The Description written to iPaaS.com is derived from the ID with this prefix removed.

  • Parent placement: categories keep their own parent, or fall back to the Default Parent Category For Categories setting when they have none. Collections have no parent in Catsy, so they are placed under the Default Parent Category For Collections setting.

iPaaS.com Caveats

  • Name matching: when no external-ID link exists yet, records are matched by Name. Ensure category and collection names are accurate so the correct iPaaS.com Category is reused.

Integration Flow

  1. A Catsy category or collection is created or updated, or a Manual Sync is triggered using the Catsy ID.

  2. The incoming record is matched to an existing iPaaS.com Category by its saved external ID, or by Name when no external-ID link exists yet.

  3. If the record names a parent category that has not yet been transferred, the parent category is transferred first so the child can be linked to it.

  4. The Category record is created or updated in iPaaS.com with the mapped values.

  5. The Catsy ID is saved as the external ID in iPaaS.com, and the transfer result is logged.

Mappings

Add/Update Catsy Category TO iPaaS.com

Description

This collection creates or updates iPaaS.com Category records from Catsy categories and collections. It maps the category name, parent relationship, description, and selected custom values.

Mapping Type

Source (Catsy)

Destination (iPaaS.com)

Description

Field

Name

Name

Sets the iPaaS.com Category name from the Catsy category name. Required.

Dynamic Formula

if the parent ID begins with Cat or Col, resolve it to the matching iPaaS.com category; otherwise pass it through

ParentId

Sets the parent of the iPaaS.com Category so records keep their place in the hierarchy. Recommended.

Dynamic Formula

"Catsy " followed by the ID with its type prefix removed

Description

Sets the category description (for example, Cat4000696937 produces "Catsy 4000696937"). Recommended.

Dynamic Formula

the Catsy category's key property

Key (custom field)

Populates the Key custom field. Optional.

Dynamic Formula

the category's bucket values joined into a comma-separated list

Buckets (custom field)

Populates the Buckets custom field. Optional.

Error Handling

Errors encountered during category transfers appear in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs. For the full list of category errors, their causes, and resolutions, see the Catsy Error Messages article.

Validation and Testing

Validation Checklist

  • The Catsy ID is entered with the correct Cat or Col prefix and exact casing.

  • The category Name is present.

  • The parent category exists or is transferred automatically as a prerequisite.

  • After transfer, confirm the Category appears in iPaaS.com under the expected parent.

Additional Notes

  • Deleted records: deleting a category or collection in Catsy is not propagated to iPaaS.com. See the Catsy Integration Known Limitations for details.

  • Custom fields: Key and Buckets are populated as iPaaS.com custom fields on the Category.

  • Category sets: Catsy category sets are outside the scope of this collection.

Related Documents

Did this answer your question?