Workflows in ItemPath are designed to automate specific conditional logic, report distribution, and cross-feature actions. Knowing when to use a workflow versus native feature settings ensures your system runs efficiently without unnecessary overhead.
Avoid Using Workflows for Standard Data Pull / Data Push Polling
Key Rule: You do not need a workflow to run routine Data Pull or Data Push integrations on a schedule.
Data Pull and Data Push already feature native, built-in polling capabilities to handle continuous background syncing (such as checking for new orders every minute).
Setting up a workflow simply to trigger a Data Pull or Data Push every __ minutes creates redundant system overhead, effectively doubling the processing effort for a job ItemPath natively manages on its own. Instead, rely directly on the automated schedule settings within your Data Pull or Data Push integration configuration.
Recommended Use Cases for Workflows
Workflows should be reserved for scenarios where triggers depend on specific criteria, events, or integrations outside of basic polling:
- Triggering "Automatic" Order Builder Integrations: Workflows are required to run Automatic Order Builder integrations when conditions are met.
- Conditional Data Pull / Data Push: When an integration should only fire based on specific report criteria rather than running continuously on a timer.
- Notifications Based on Report Criteria: Automatically emailing or texting stakeholders when specific conditions are met in a report.
- Scheduled Report Distribution: Sending recurring email copies of specific reports to stakeholders.
- Triggering Lights Integrations: Driving visual indicators in your warehouse based on system events.
