Issues
Emit an event when GitHub delivers the issues webhook.
Workflow template
Keep one row per GitHub issue in your engineering database. Select a unique external_id column. Connect GitHub and select a repository. Connect PostgreSQL and choose a schema and an existing table. Match the mapped column names to your table. Enable the workflow once both sides are configured.
How it works
Emit an event when GitHub delivers the issues webhook.
Insert a row or update mapped columns when a unique key already exists. Use a stable key for repeatable delivery.
Before activation
Open the template in FastHook to create an editable Workflow Draft.
Connect your accounts for GitHub, PostgreSQL.
Review the Steps, field mappings, routes, and provider settings.
Activate the Workflow when the Draft is ready, then verify a test run.
No. FastHook creates a disconnected Draft. Connect your own GitHub, PostgreSQL accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.
Append newly opened pull requests to a review intake table.
View template →Maintain a release register keyed by unique external_id.
View template →