Case study
Marketing Requests
Slack form → Asana → native S3-to-SFTP copy in Content System, then complete, comment the editor, and unassign ops.
- Client
- Streaming content ops
- Services
- Automation · Integrations · Internal tools
01 / Challenge
Other teams needed FAST and promo cuts from masters in the upload bucket. Slack forms became Asana tasks, then a scavenger hunt: find the paths, run a copy, tell the editor, and remain tagged on the parent for the rest of edit/review noise.
02 / Insight
The painful part was not the copy — it was staying tagged on someone else’s edit process after your job was done. The native workspace is where the objects actually move.
03 / System
Slack form → Asana (tag + email) is intake. The file move is Content System → Marketing Request: paste paths, copy on the ops host over JSON-line SSH, no AWS secrets in the Mac app. On success: complete the sub-task, comment the editor with the destination folder, unassign content ops from the parent. The screens here are that native workspace — not a flowchart mock.
Process reconstruction
Marketing Requests architecture
How the pieces hand off without another dashboard nobody opens.
- Slack
- Asana
- S3 copy
- Unassign
04 / Execution
Slack form → Asana (tag + email) is intake. The file move is Content System → Marketing Request: paste paths, copy on the ops host over JSON-line SSH, no AWS secrets in the Mac app. On success: complete the sub-task, comment the editor with the destination folder, unassign content ops from the parent. The screens here are that native workspace — not a flowchart mock.
05 / Outcome
Paste-and-done. Editors get a folder. Ops leave the thread. The ticket system stays Slack and Asana; the dangerous part (credentials, copy, status) sits in the console that already knew how to talk to the host.
Toolkit
Every surface, featured fully.
Each piece below is almost its own product — designed, shipped, and used as a first-class workflow rather than a buried submenu.
01
Native Marketing Request
The file move is a first-class workspace inside Content System — not a bot that silently copies. Paste campaign paths, confirm the source objects, stage to the marketing SFTP share, and read the outcome in Activity. Under the hood it is the same JSON-line SSH channel as upload: the Mac does not hold AWS secrets; the ops host does the copy with the session profile.
02
Slack form → Asana
Intake is a Slack form that becomes an Asana task with automations that tag content ops and send email. That is the ticket. It is intentionally not a new request portal. People were already in Slack.
03
Complete, comment, unassign
On a successful copy, Asana gets three calls: complete the content-ops sub-task, comment the editor with the destination folder, and unassign the operator from the parent. The last one is the actual product. Staying tagged on someone else’s edit/review thread was the hidden cost of being helpful.
Native Marketing Request UI in Content System.
Asana complete + comment + unassign on success.
Editors get a destination, not a scavenger hunt.