Open a GitHub issue in one repository for each accepted submission.
Availability: awaiting provider verification. The connector is built and tested against recorded responses, but it has not yet passed a live test against GitHub, so it is off by default and shown as "Implemented, awaiting provider verification". Installing as a GitHub App and syncing issue status back are not available yet.
What you need
- A fine-grained access token limited to the one repository, with Issues: read and write.
What you configure
- Access token and repository as
owner/name. - Title field - defaults to
name; falls back to the form name and submission id. - Labels - optional, comma-separated. GitHub drops labels if the token lacks push access.
What Formspring sends
An issue with the title above and a body listing the answers as plain text in a code block, followed by a line naming the form and submission it came from. Answers cannot mention people or teams.
Steps
- In GitHub, create a fine-grained token for the repository with Issues read and write.
- In Formspring, open your form → Integrations → GitHub → fill the fields → Save.
- Submit a test and confirm the issue and a 2xx in Deliveries.
Tips
- GitHub limits how fast content can be created. A rate-limited delivery is retried automatically.
- Keep the token scoped to one repository so a leak cannot reach anything else.
