Overview
Gather files from several source devices into one collection destination on a repeating schedule, and execute additional tasks after each collection workflow completes.
Collect Files from Many Devices on a Recurring Schedule With Follow-Up Actions
Automate recurring file collection from multiple source devices and configure follow-up actions after collection completion.
- Collect files
- Many devices
- On a recurring schedule
- Follow-up actions
'%3e%3cpath%20d='M8.65045%208.65041H13.2006V13.2006H8.65045V8.65041ZM3.60107%208.65041H8.15125V13.2006H3.60107V8.65041ZM8.65045%203.60059H13.2006V8.15076H8.65045V3.60059ZM3.60107%203.60059H8.15125V8.15076H3.60107V3.60059Z'%20fill='%23FFFFFF'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_571_17866'%3e%3crect%20width='9.6'%20height='9.6'%20fill='white'%20transform='translate(3.6001%203.60059)'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e){kind=small}
'%3e%3cpath%20d='M15.9761%207.98019C15.9761%2012.3873%2012.4032%2015.9602%207.99588%2015.9602C3.58838%2015.9602%200.015625%2012.3873%200.015625%207.98019C0.015625%203.57281%203.5885%200%207.99588%200C12.4033%200%2015.9761%203.57281%2015.9761%207.98019Z'%20fill='%23DD4814'/%3e%3cpath%20d='M2.56855%206.91436C1.97987%206.91436%201.50293%207.39129%201.50293%207.97998C1.50293%208.56836%201.97987%209.04536%202.56855%209.04536C3.15699%209.04536%203.63393%208.56836%203.63393%207.97998C3.63393%207.39129%203.15699%206.91436%202.56855%206.91436ZM10.1757%2011.7567C9.66618%2012.0511%209.49137%2012.7024%209.78574%2013.2117C10.0798%2013.7213%2010.7311%2013.896%2011.2407%2013.6017C11.7502%2013.3076%2011.925%2012.6564%2011.6307%2012.1467C11.3366%2011.6374%2010.685%2011.4627%2010.1757%2011.7567ZM4.88287%207.97998C4.88287%206.92711%205.40587%205.99686%206.20605%205.43361L5.42712%204.12898C4.49499%204.75211%203.80137%205.70423%203.51312%206.81942C3.84949%207.09379%204.06474%207.51161%204.06474%207.97992C4.06474%208.44798%203.84949%208.86579%203.51312%209.14023C3.80099%2010.2557%204.49462%2011.2079%205.42712%2011.831L6.20605%2010.526C5.40587%209.96311%204.88287%209.03292%204.88287%207.97998ZM7.99487%204.86767C9.62068%204.86767%2010.9546%206.11417%2011.0946%207.70392L12.6127%207.68154C12.5381%206.50792%2012.0253%205.45429%2011.2376%204.67954C10.8324%204.83261%2010.3644%204.80917%209.96005%204.57604C9.55487%204.34223%209.3008%203.94779%209.23137%203.51967C8.82862%203.40825%208.41268%203.35169%207.9948%203.35154C7.28329%203.35085%206.58125%203.51477%205.94362%203.83048L6.68393%205.15717C7.09452%204.96607%207.54199%204.86725%207.99487%204.86767ZM7.99487%2011.092C7.54201%2011.0925%207.09456%2010.9936%206.68399%2010.8025L5.94368%2012.1291C6.58122%2012.4452%207.28333%2012.6093%207.99493%2012.6085C8.41282%2012.6085%208.82877%2012.5518%209.23143%2012.44C9.30087%2012.0119%209.55499%2011.6178%209.96005%2011.3836C10.3648%2011.15%2010.8325%2011.127%2011.2376%2011.2801C12.0254%2010.5054%2012.5381%209.45173%2012.6128%208.27811L11.0942%208.25573C10.9546%209.84592%209.62074%2011.092%207.99487%2011.092ZM10.1754%204.20254C10.685%204.49679%2011.3363%204.32254%2011.6303%203.81292C11.9247%203.30329%2011.7503%202.65198%2011.2407%202.35761C10.7311%202.06361%2010.0798%202.23823%209.78537%202.74786C9.49143%203.25723%209.66612%203.90848%2010.1754%204.20254Z'%20fill='%23FFFFFF'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_571_17880'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e){kind=small}
Start conditions
When should it start?
File options
After transfer
You can add more than one action.
What should happen after the transfer?
Get your integration code
Select a development language to generate sample code for this configuration.
Sign in to download
You can download the complete sample code for the configuration set above.
How to use the downloaded code
Apply the downloaded code and explore more examples.
AI-FRIENDLY EXPLANATION
How this solution works
This page shows how to collect files from multiple source devices into a single collection destination on a recurring schedule and run follow-up actions after each collection completes. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.
Key components
- Multiple source devices (e.g., Windows)
- Collection destination
- Recurring collection schedule
- Follow-up actions (after collection)
How it fits your workflow
Use this solution for routine collection that always has a next step. A notification, archive, or processing script belongs to every cycle rather than to a separate manual task.
Common use cases
- Collect daily logs and refresh a dashboard
- Gather weekly reports and send a summary
- Pull nightly backups and archive each run
- Consolidate shift data and start processing
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
Can recurring collection trigger follow-up actions?
Configure follow-up actions when the selected workflow supports them.
Do follow-up actions run after every collection cycle?
Verify the action trigger and completion conditions for each scheduled execution.
How do I monitor recurring collection?
Review execution history, source-level collection results, and available logs.