Short answer: You can upload gcs object in Google Cloud Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Cloud Storage Upload GCS Object action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Bucket bucket | string | Optional | – |
Object Name (path) name | string | Required | uploads/file.png |
File content (URL/base64/raw) content | string | Required | – |
Content Type contentType | string | Optional | – |
{"bucket": "{{trigger.bucket}}","name": "uploads/file.png","content": "{{trigger.content}}","contentType": "{{trigger.contentType}}"}
{"name": "uploads/file.png","size": "12345","bucket": "my-bucket","mediaLink": "https://storage.googleapis.com/...","contentType": "image/png"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.