Short answer: Drop the "GitHub → Create Pull Request" 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 |
|---|---|---|---|
Repository Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository Name repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
Title title | string | Required | Title. Example: Fix login redirect bug |
Head Branch head | string | Required | The branch that contains your changes |
Base Branch base | string | Required | The branch you want to merge into |
Description body | string | Optional | PR description (supports GitHub Markdown) |
Draft PR draft | options | Optional | Draft PR. Options: No (ready for review), Yes (draft) |
{"owner": "e.g. acme-corp","repo": "e.g. my-project","title": "e.g. Fix login redirect bug","head": "e.g. fix/login-redirect","base": "e.g. main"}
{"base": {"ref": "main"},"head": {"ref": "fix/login-redirect"},"draft": false,"state": "open","title": "Fix login redirect bug","number": 99,"html_url": "https://github.com/acme-corp/my-project/pull/99","created_at": "2025-01-15T12:00:00Z"}
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.