Questions answered, time saved: Your FAQs on PlentyONE Flow and the Flow Agent

When individual processes, event actions, and tools each follow their own logic and constraints, errors often go unnoticed until orders or listings have already been affected.

When exceptions and special cases also increase with each marketplace, maintaining and monitoring workflows becomes an ever-greater drain on your time. To eliminate this operational bottleneck once and for all, we developed PlentyONE Flow.

A Look Behind the Scenes: PlentyONE Flow and the Flow Agent

PlentyONE Flow combines actions, events, and multi-step processes into a single feature. You can chain steps together, set conditions, and integrate human approvals directly. The new Flow Agent provides additional support with AI.

In the live webinar “Smarter Automation,” Jan Griesel and Product Manager Jacqueline Wendel demonstrated Flow and the Flow Agent live.

The Q&A session that followed delved deeply into practical applications. These topics are relevant to far more than the approximately 280 participants. That’s why we’re documenting the most important questions and answers here for the entire PlentyONE user community.

What Flow Already Does for You Today

• Everything in one place: Actions, events, and multi-step processes all come together in a single Flow.
• Full transparency: The Flow Tracker shows every step and every execution.
• You stay in control: Interactive actions pause the Flow until you approve them.
• Time windows instead of fixed times: Flows start at intervals as short as 15 minutes and reliably process even large volumes of tasks.
• AI support scales with you: The Flow Agent creates, explains, and optimizes flows on demand.

Your questions from the webinar, answered briefly and concisely

The live Q&A session brought together many practical questions. Here are the most important answers, grouped by topic.

Technology and Reliability in Everyday Use

How many orders does a flow process at once? Up to 200 orders per run. The recurring 15-minute cycle reliably handles even large volumes.

What happens if two flows respond to the same trigger? Both flows will then run in parallel. Set additional filters on the trigger to control this specifically.

PDF creation and sending in a single step—is that secure? Separate document creation and email sending into two distinct Flows. This way, Flow reliably processes both steps one after the other.

What happens in the event of an external disruption? The flow pauses if an external system is unreachable. After the disruption, the flow automatically processes the resulting backlog using increased computing capacity.

The Flow Agent (AI)

What can the Flow Agent do so far? It explains and analyzes existing flows. It creates new flows from templates or based on your description. It searches flows specifically for individual actions and assists with the migration of event actions.

Does the Flow Agent automatically make changes? No. It asks for permission before every action. Deleting, activating, and deactivating remain entirely up to you.

Can I provide the Flow Agent with company-specific context? Yes. Your own system data, such as statuses or shipping profiles, is incorporated. Your data remains within your system. Nevertheless, you should carefully consider what data you share with AI.

When does the beta phase for the Flow Agent start? In the coming weeks. We’ll let you know as soon as registration opens.

What’s Next

Will Flow get improved error handling? Yes. A new control element for error handling is currently being developed. The Flow Agent is learning this topic in parallel.

Will there be Flows for contacts and products? Yes, both are in the works. Product automation will initially launch with a more limited set of features.

Will Flow respond to external webhooks in the future? Currently, Flow calls external URLs; the reverse functionality isn’t available yet. We’re discussing incoming webhooks for a future version.

Transition and Migration

Do I need to switch my event actions right away? No. Event actions will continue to run unchanged through 2026. There is no shutdown date yet. However, we recommend familiarizing yourself with Flow as early as possible and not waiting too long to make the switch. This will give you enough time to get up to speed and adapt existing processes in a timely manner.

Will everything run twice during the transition? Actively avoid duplicate runs. Activate the new Flow and deactivate the old event action or process immediately afterward.

Are marketplace actions from plugins already available in Flow? Yes. Plugin actions from event actions are mirrored 1:1 in Flow. Please let us know if an action is missing.

How far along is the migration of the old processes? Flow covers 80 to 90 percent of the previous process actions. The picklist will follow shortly, with additional document types to come afterward.

How to Make the Transition Stress-Free

Use the built-in migration feature for a seamless transition. The Flow Agent also helps you merge similar workflows. Never run old and new automations in parallel for the same scenario.

Operations continue automatically in the background as soon as a Flow is active. The only extra effort required is during the setup itself.

⚠️ Keep these dates on your radar

• Action Manager: Shutdown in October 2026. Migrate affected workflows to Flow now.
• Event Actions: No decommissioning date in 2026. An announcement of a date is expected in the first half of 2027—not during the holiday shopping season and not immediately afterward.
• Our recommendation: Get started with Flow early. Event actions will continue to run without any time pressure.

Want to know all the details?

Watch the full recording of the “Smarter Automation” webinar (german only): Watch the webinar recording.