Create a GitHub issue from feedback
Configure a webhook with a stored token, or use a receiver to transform arbitrary comments safely.
Choose a direct request or a receiver
Pollenate can call GitHub's create-issue API through a webhook rule. This is an explicit automation, not a built-in issue synchronization service.
Use a direct request when the body consists of static text and constrained identifiers. Use a receiver you control when the issue must contain arbitrary customer comments: the receiver can safely JSON-encode text, deduplicate events and decide what belongs in the repository.
GitHub's create-issue reference documents POST /repos/OWNER/REPO/issues and its required permissions. A fine-grained token needs access to the selected repository and Issues write permission. Save the token as a named Pollenate secret, such as GITHUB_TOKEN.
Configure a direct webhook
Create an inbox rule for feedback.created with an appropriate filter.
| Setting | Value |
|---|---|
| Target | https://api.github.com/repos/OWNER/REPO/issues |
| Method | POST |
| Accept header | application/vnd.github+json |
| Authorization header | Bearer {{secrets.GITHUB_TOKEN}} |
| Content-Type header | application/json |
A body with a generated feedback ID and static text avoids interpolating arbitrary user text:
{
"title": "Feedback {{data.feedbackId}} needs review",
"body": "Review the originating feedback in Pollenate.",
"labels": ["feedback"]
}Create the feedback label in the repository or omit the labels field. Do not insert a free-text comment directly between JSON quotes: template substitution does not escape quotation marks and newlines.
Testing this rule sends a real GitHub request and can create a real issue. Use a test repository, inspect GitHub's response, and then check an intentional end-to-end feedback submission.
Include comments through a receiver
For richer issues, let Pollenate send its default signed event envelope to your receiver:
- Verify the webhook signature against the raw body.
- Check the event type and deduplicate by
feedbackId. - Build a GitHub request object from the approved fields.
- Send the request using
JSON.stringify, keeping the GitHub token server-side. - Store the issue number/URL and acknowledge the event.
const issue = {
title: "Product feedback " + event.data.feedbackId,
body: [
"Feedback type: " + event.data.type,
"",
event.data.comment ?? "(No comment supplied)"
].join("\n")
};
const response = await fetch(
"https://api.github.com/repos/OWNER/REPO/issues",
{
method: "POST",
headers: {
Authorization: "Bearer " + process.env.GITHUB_TOKEN,
Accept: "application/vnd.github+json",
"Content-Type": "application/json"
},
body: JSON.stringify(issue)
}
);
if (!response.ok) throw new Error("GitHub returned " + response.status);
const createdIssue = await response.json();This excerpt assumes signature verification, durable deduplication and input checks have already run.
Link the result back
The webhook dispatcher does not automatically write GitHub's response into Pollenate. Link the issue in the feedback UI, or update the feedback event with externalTrackerType: "github", externalTrackerId and externalTrackerUrl through the feedback API.
A GitHub 401 points to token validity, a 403 to permissions or policy, and a 422 to request fields such as an invalid label. Check the response body. Repeatedly testing a successful rule can create duplicate issues.