Short answer: Drop the "GitHub → Delete 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: docs/readme.md |
Commit Message message | string | Required | Commit Message. Example: Remove obsolete file |
Branch branch | string | Optional | Git branch name. |
{"owner": "e.g. octocat","repo": "e.g. hello-world","path": "e.g. docs/readme.md","message": "e.g. Remove obsolete file","branch": "e.g. main"}
{"commit": {"sha": "def456","message": "Delete file"}}
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.