Purpose
1.2. Automate sharing of converted files through secure channels to team members, stakeholders, and project directories.
1.3. Automate tracking and logging of conversion and sharing actions for version control and compliance.
Trigger Conditions
2.2. File status updated to “ready for review” in a project management tool.
2.3. Request form submission for specific file formats by a stakeholder.
2.4. Scheduled batch conversion and distribution (e.g., end-of-week export).
Platform Variants
• Feature/Setting: Design Automation API, configure workflows to automate conversion from RVT to DWG or PDF, provide callback for post-conversion actions.
3.2. Microsoft Power Automate
• Feature/Setting: File automation flows, use “Convert file” and “Share file” actions for SharePoint directories.
3.3. Zapier
• Feature/Setting: Multi-step Zap for automated file intake, conversion with CloudConvert, and automated sharing via Dropbox, Google Drive, or Slack.
3.4. CloudConvert
• Feature/Setting: Automate “convert” API for DWG, PDF, SKP formats, with webhook notifications for process completion.
3.5. Dropbox
• Feature/Setting: Automated folder workflows with Dropbox API to detect new files, fetch, and share converted versions automatically.
3.6. Google Drive
• Feature/Setting: Drive API to automate monitoring folders, triggering conversion functions, and setting automated sharing permissions.
3.7. Trimble Connect
• Feature/Setting: Automate project file updates, convert IFC/SKP, and auto-synchronize with team spaces via integration APIs.
3.8. Box
• Feature/Setting: Automation with Box Skills for file processing, use API for auto-sharing and file event triggers.
3.9. Slack
• Feature/Setting: Slack Bots API to automate file delivery notifications and direct file sharing in target channels or DMs post-conversion.
3.10. Microsoft Teams
• Feature/Setting: Graph API to automate sending notifications and files to Teams channels or chats after a file conversion event.
3.11. BIM 360
• Feature/Setting: Data Management API to automate detection of new design files, initiate conversion, and distribute to collaborators.
3.12. Egnyte
• Feature/Setting: Workflow Automation engine to auto-convert incoming architecture files and push shared links to designated teams.
3.13. Smartsheet
• Feature/Setting: Automated actions via Workflow Builder for tracking requests, file conversion tasks, and sharing documents.
3.14. Asana
• Feature/Setting: Automated task creation and file sharing actions based on file conversion completion via API.
3.15. Monday.com
• Feature/Setting: Automate board triggers to convert uploaded design documents and automatically attach results to tasks.
3.16. OneDrive
• Feature/Setting: File watcher automation to detect and convert files, then automate sharing links with the correct team permission set.
3.17. Airtable
• Feature/Setting: Automation triggers for file conversion requests and auto-populate logs of converted and distributed files.
3.18. Notion
• Feature/Setting: Automate new file logs and notifications; link automator scripts for “converted file” entries in project pages.
3.19. Trello
• Feature/Setting: Power-Up integrations for task-card automation to upload, convert, and distribute architectural files.
3.20. Email (SMTP/IMAP)
• Feature/Setting: Automated detection of attached files, pass through conversion service, automatedly email converted results to recipients.
3.21. WebDAV Servers
• Feature/Setting: Automate monitoring directories, converting files on-upload, and sharing via secure automatable file links.
Benefits
4.2. Ensures automated consistency in file versions and distribution.
4.3. Reduces human errors through reliable automation of sharing permissions.
4.4. Accelerates collaboration by automating file delivery across multiple channels instantly.
4.5. Enhances transparency and compliance with automated tracking of all conversion and sharing actions.