Channel-Feed Loop

The Channel-Feed Loop feature allows you to automatically run a Feed immediately after its linked Channel finishes processing. This eliminates manual steps, reduces delays, and ensures consistent product data propagation across related products.

This guide explains what Channel-Feed Loop does, how to set it up, and how to use it effectively.

What Is Channel-Feed Loop?

Channel-Feed Loop is a native automation that triggers a Feed to run as soon as a Channel completes. This is especially useful when:

• Parent product updates need to be applied to child products
• Variant products must stay synchronised
• Kit or bundle components need attribute updates
• Any product group depends on another group's data
• Parent product data depends on data stored on Child products

Instead of manually running the Feed or relying on scheduled delays or external scripts, Pimberly now handles both steps automatically.

How It Works

1. A Channel runs as normal.
2. Once the Channel finishes, Pimberly immediately triggers the linked Feed.
3. The Feed imports or updates product data based on the Channel’s export.
4. Safeguards prevent invalid or recursive mappings to keep workflows stable.

Setting Up a Channel-Feed Loop

Step 1 — Enable the Channel-Feed Loop Connector on a Channel

1. Go to Admin → Products → Channels.
2. Create a new Channel or open an existing one.
3. In the Product Connector section, enable the Channel-Feed Loop connector type.
4. If you're working on an existing channel, change the Status to Disabled.
5. Save the Channel.

Step 2 — Create or Configure the Linked Feed

1. Go to Admin → Products → Feeds.
2. Create a new Feed or open an existing one.
3. In the Product Connector section, select Channel-Feed Loop.
4. Choose the Channel you want this Feed to listen to.
5. Map the attributes as required.
6. Save the Feed.

Using the Channel-Feed Loop

Once the setup is complete:

• Run the Channel manually or enable it and let it run on its schedule.
• When it finishes, the Feed will automatically start.
• The system validates mapping restrictions to prevent loops or invalid updates.

What You’ll See in the Feed Log

• Channel run appears as normal.
• A Feed run is automatically created immediately after, marked as triggered by Channel-Feed Loop.

Best Practices

• Ensure the Feed updates other products or different attributes to avoid circular workflows.
• Use product filters in the Channel to keep exported sets tight and intentional.
• Verify that your mappings do not write back to the same link ID used by the Channel.

Troubleshooting

Feed did not run after the Channel

• Check that both the Channel and Feed have the Channel-Feed Loop connector enabled.
• Verify the Feed is linked to the correct Channel.
• Ensure the Feed is not currently running — the Channel will log an error if it can’t trigger the Feed.

Mapping validation errors

The system blocks mappings that would cause recursive updates. Update your Feed mappings to target different products or attributes.

Demo Video

Need Help?

If you have questions or your workflow requires a more advanced configuration, please contact Pimberly Support or speak to your Customer Success Manager.