Archive signed agreements by customer and year.
Storage / native route
Cloudbox
meets Relay.
File completed documents into consistent folders with names your whole team can find.
Request connection ↗CloudboxDocument approved
01WHEN
RRelaylogic + routing
02THEN
✓Action completeStore and share file
Connection overview
Keep work in motion.
Cloudbox keeps workflow outputs organized after approval. Dynamic folder paths make the archive predictable without manual cleanup.
ROUTE SPEC / CLOUDBOX
- Trigger
- Document approved
- Action
- Store and share file
- Connection
- Native
- Setup
- ~5 minutes
Field notes / common routes
Put it to work.
Create a project folder when onboarding begins.
Share final assets with a delivery team.
Connection protocol
Three stops to live.
- 1
Connect the Cloudbox account that owns your shared folders.
- 2
Choose a destination and define a naming pattern.
- 3
Test with a sample file before enabling the workflow.
Signal notes / FAQ
Cloudbox questions
Can Relay avoid duplicate files?
Include a unique record ID in the filename and choose replace or skip behavior.
Can workflows create folders?
Yes. A route can create nested customer or project folders before saving a file.