Short answer: Drop the "GitHub → Get File" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
File Path path | string | Required | File Path. Example: src/main.js |
Branch / Tag / SHA ref | string | Optional | Branch / Tag / SHA. Example: main |
{"owner": "e.g. octocat","repo": "e.g. Hello-World","path": "e.g. src/main.js","ref": "e.g. main"}
{"sha": "abc123","name": "main.js","path": "src/main.js","size": 1024,"content": "Y29uc29sZS5sb2coJ2hlbGxvJyk=","encoding": "base64","html_url": "https://github.com/octocat/Hello-World/blob/main/src/main.js"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.