D
Daniel Fundi Ndaya
TRIGGERS
  • File uploaded to Media Storage → start a workflow
  • File deleted from Media Storage → fire a notification or cleanup sequence
  • Folder created in Media Storage → kick off a project or onboarding flow
  • File updated or replaced in Media Storage → alert the team or update a contact field
ACTIONS
  • Upload a file to a specific Media Storage folder (from a form, a URL, or another step in the workflow)
  • Create a folder in Media Storage — name it dynamically using contact name, date, pipeline stage, or any custom field
  • Get a file URL from Media Storage and attach it to a contact record, opportunity, or conversation thread
  • Move or copy a file between Media Storage folders
  • Delete a file or folder from Media Storage when a project closes
  • Rename a file inside Media Storage
  • List files in a folder (use this for conditional branching — does this project folder have assets yet?)
  • Search Media Storage for a file by name or type
Here’s what this actually looks like when it’s live:
You’re an agency owner. Your client submits an intake form. Files come in — logo, photos, copy docs. A workflow fires. It creates a named folder in Media Storage, moves those files in, grabs the folder URL, and attaches it to the contact record. Your team gets a notification with the link. Nobody touches a file manually. That’s the onboarding flow you’ve been trying to build since you started.
You work with contractors. One of them finishes a deliverable and uploads it through a form. A trigger fires. The task gets marked complete in the CRM. The file URL gets attached to the opportunity. The client gets an automated message with the link. The handoff runs itself. No back-and-forth. No “did you get my file?”
You run a community or course. A new member joins. A workflow builds their folder in Media Storage, uploads their welcome kit, grabs the URL, and sends them access via automation. Works at 3am. Works for your 500th member the same way it worked for your first.
You’re running a campaign. The client’s brief form comes in with image files. Those files land in an organized project folder in Media Storage automatically. Your team sees them instantly. Nobody’s emailing “can you resend those assets?”
The project is done. A workflow pulls the final deliverable from Media Storage, injects the URL into a message, and sends it to the client. No manual attachment. No back-and-forth. It just goes.
This isn’t about adding complexity. It’s about closing the loop on something that’s already half-built.
Media Storage is already where the files live. It’s already connected to everything that matters. All it needs is the automation layer to go with it.